chore(release): align package.json with published v5.0.0 - #59
Merged
Conversation
The v5.0.0 release ran semantic-release with no config file: the workflow installed @semantic-release/git via extra_plugins but never added it to the plugin chain, so the default plugin set ran and the version write-back commit was never created. The current .releaserc.json already lists the git plugin; this aligns the stale 4.4.2 version string with the published release. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Aligns the library’s declared package version with the already-published v5.0.0, so consumers and release tooling no longer see a stale package.json version.
Changes:
- Bump
package.jsonversion from4.4.2to5.0.0.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Contributor
|
🎉 This PR is included in version 5.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Problem
package.jsonsays4.4.2while npm and GitHub releases sit at v5.0.0, and nochore: releasewrite-back commit exists in history. Every consumer-facing version string andvp packoutput is a full major behind.Root cause
Same defect as pas-js#41. The v5.0.0 release (2026-03-19) ran semantic-release with no configuration: the repo had no
.releaserc.jsonand noreleasekey inpackage.json. The workflow passed@semantic-release/gitthrough the action'sextra_pluginsinput, butextra_pluginsonly installs packages — it does not add them to the plugin chain. semantic-release therefore ran its default plugin set (commit-analyzer,release-notes-generator,npm,github), which excludes the git plugin, so the version write-back never executed.The later
.releaserc.jsonconfigures@semantic-release/gitcorrectly, and the release job now matches putio-sdk-typescript, where write-back commits provably land (chore(sdk): release 11.2.0 [skip ci],package.json= npm = 11.2.0). No release-triggering commit has landed here since March (onlychore/ci/build), so the pipeline never got a chance to self-heal the stale version.Solution
Align
package.jsonto the published v5.0.0. semantic-release computes the next version from thev5.0.0git tag (onmain), so the nextfix/featrelease computes correctly and its write-back commit will land through the already-fixed pipeline.chorecommit type on purpose: merging this does not trigger a no-op publish.Verification
vp run verifygreen locally: 3 test files, 10 tests passed.Fixes #58