Skip to content

fix(ci): use npm pkg set to write version to package.json before publish#782

Merged
danadajian merged 1 commit into
mainfrom
fix/pnpm-publish-version-flag
May 27, 2026
Merged

fix(ci): use npm pkg set to write version to package.json before publish#782
danadajian merged 1 commit into
mainfrom
fix/pnpm-publish-version-flag

Conversation

@danadajian
Copy link
Copy Markdown
Contributor

Summary

  • The publish workflow was calling pnpm version with --workspaces-update false to bump the version in comparadise-utils/package.json before publishing to npm
  • pnpm's version subcommand does not support this flag (it's npm-only), causing the publish job to fail
  • npm pkg set is a direct JSON write to package.json with no git commits, no workspace traversal, and no pnpm involvement — the right tool for this job

Changes

  • Replaced pnpm version $NEW_VERSION --workspaces-update false with npm pkg set version=$NEW_VERSION in the publish workflow

Test plan

  • Trigger a release and confirm the publish-comparadise-utils job completes without error
  • Confirm the published package on npm has the correct version

Generated with Claude Code

pnpm's version subcommand does not support workspace-related flags.
npm pkg set writes directly to package.json with no git or workspace side effects.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@danadajian danadajian merged commit 127a649 into main May 27, 2026
3 checks passed
@danadajian danadajian deleted the fix/pnpm-publish-version-flag branch May 27, 2026 18:57
@eg-oss-ci
Copy link
Copy Markdown

🎉 This PR is included in version 1.44.4 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants