Skip to content

fix(release): set version when publishing oh-my-openagent#2651

Merged
code-yeongyu merged 1 commit intodevfrom
fix/openagent-version-in-publish
Mar 17, 2026
Merged

fix(release): set version when publishing oh-my-openagent#2651
code-yeongyu merged 1 commit intodevfrom
fix/openagent-version-in-publish

Conversation

@code-yeongyu
Copy link
Copy Markdown
Owner

@code-yeongyu code-yeongyu commented Mar 17, 2026

Fixes the publish workflow not setting version for oh-my-openagent package. Was trying to publish with base package.json version (3.11.0) instead of the release version.


Summary by cubic

Fixes the publish workflow to set the release version when publishing oh-my-openagent, so npm publishes the correct version and avoids version conflict errors.

  • Bug Fixes
    • In .github/workflows/publish.yml, set package.json .version to ${{ steps.version.outputs.version }} and .name to oh-my-openagent.
    • Align optionalDependencies names to oh-my-openagent-* and set their versions to the same release version.

Written for commit 9b8aca4. Summary will update on new commits.

The publish step was updating name and optionalDependencies but not
version, causing npm to try publishing the base package.json version
(3.11.0) instead of the release version (3.12.0).

Error was: 'You cannot publish over the previously published versions: 3.11.0'
@code-yeongyu code-yeongyu merged commit 576ff45 into dev Mar 17, 2026
1 check passed
@code-yeongyu code-yeongyu deleted the fix/openagent-version-in-publish branch March 17, 2026 17:15
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Requires human review: Not 100% sure of no regressions; the jq transformation for optionalDependencies may fail if the key is missing from package.json, potentially breaking the publish workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant