chore(js): bump package to 0.1.1 for npm release - #44
Merged
Conversation
envoic@0.1.0 was previously published then unpublished on npm, so the registry permanently refuses to republish 0.1.0 (the v0.1.0 release got "Cannot publish over previously published version 0.1.0"). Bump the JS package to 0.1.1 so it can ship and realign with PyPI. The Python package needs no change: its version is derived from the git tag (hatch source = "vcs"), so tagging v0.1.1 yields 0.1.1 automatically.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe version field in ChangesVersion Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the JS package (
packages/js) from0.1.0to0.1.1.Why
envoic@0.1.0was published then unpublished on npm back in February, and npm permanently reserves unpublished version numbers. Thev0.1.0release therefore failed with:0.1.0can never go to npm, so the JS package needs a fresh version to ship. PyPI already has0.1.0; moving both to0.1.1realigns them.Scope
packages/js/package.json+package-lock.json(rootenvoicversion). Theyocto-queuedependency entry is untouched.[tool.hatch.version] source = "vcs"), so taggingv0.1.1yields0.1.1automatically.This must merge together with #43 (
--allow-same-version) before cutting the release. Otherwise thev0.1.1release re-hits "Version not changed", sincepackage.jsonwill already be at0.1.1.Release steps (after both merge)
v0.1.1→ Python publishes to PyPI, JS publishes to npm.npm view envoic versionshows0.1.1.Summary by CodeRabbit
0.1.0to0.1.1.