Skip to content

Conversation

sjungling
Copy link
Member

Since we removed @semantic-release/npm plugin, we need to manually
sync the version that semantic-release calculates in the root package.json
to the dist/package.json before publishing to npm.

  • Extract version from root package.json (updated by semantic-release)
  • Update dist/package.json version using npm version command
  • Ensures published package has correct semantic version

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

Since we removed @semantic-release/npm plugin, we need to manually
sync the version that semantic-release calculates in the root package.json
to the dist/package.json before publishing to npm.

- Extract version from root package.json (updated by semantic-release)
- Update dist/package.json version using npm version command
- Ensures published package has correct semantic version

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@sjungling sjungling merged commit cc441d3 into main Sep 23, 2025
3 checks passed
@sjungling sjungling deleted the fix/npm-version branch September 23, 2025 23:47
github-actions bot pushed a commit that referenced this pull request Sep 23, 2025
## [4.1.1](v4.1.0...v4.1.1) (2025-09-23)

### Bug Fixes

* sync version from semantic-release to dist package.json ([#4](#4)) ([cc441d3](cc441d3))
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