chore: realign version to 1.0.0 (next release publishes 1.0.1)#14
Merged
Conversation
The 0.0.x line published to npm sits below a stranded 1.0.0 (published 2025), so npm refuses to implicitly move the 'latest' tag forward to a 0.0.x release. Reset the version to 1.0.0 so a release-patch bump produces 1.0.1, which cleanly supersedes 1.0.0 and takes 'latest'.
baransu
added
the
release-patch
enzomonjardin
approved these changes
Jun 2, 2026
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
2 participants
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.
Why
The npm
@jam.dev/sdkpackage has a stranded1.0.0(published 2025-04-11) sitting above the active0.0.xline. npm refuses to implicitly move thelatestdist-tag backward from1.0.0to any0.0.xversion, which is why the last publish failed:What
Set the version to
1.0.0. On merge, therelease-patchlabel drivesnpm version patch→1.0.1, which is higher than the stranded1.0.0and therefore cleanly takeslatest— no--tagworkaround needed.On merge this will
mainto1.0.1, push the commit + tagv1.0.1(the release bot now bypasses the new branch ruleset)v1.0.1npm publish1.0.1→ becomeslatestOrphan
v0.0.7tag + GitHub Release (from the prior failed publish, never on npm) have been cleaned up.