fix(npm): promote stable publishes to the latest dist-tag#6039
Merged
SivanCola merged 1 commit intoJul 6, 2026
Merged
Conversation
The "0.x stable owns latest" rule was a migration guard from when the 1.x Go line was rc-only. Once 1.x went stable the guard inverted into a trap: latest stayed pinned at 0.53.2, so pnpm update -g / npm update -g silently downgraded every 1.x user back to the retired line, and the documented manual promotion (npm dist-tag add) never happened (esengine#5822). Stable versions now always publish under latest; rc/beta stay on next and canary stays on canary. A post-publish verify step polls the registry and fails the release if the tag did not land — the guard esengine#5822 lacked.
github-actions
Bot
added
v2
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
1 participant
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
lateston npm is still pinned at 0.53.2 while every 1.x release ships undernext/canary:Because
npm update -g/pnpm update -gresolve thelatesttag, every global update silently downgrades 1.x users to a months-old, different-architecture version (#5822). The documented escape hatch — a manualnpm dist-tag add— has never been run; manual steps get forgotten.Changes
-canary.→canary, any other prerelease →next, stable →latest, automatically.Verified the tag mapping:
1.17.1→latest,1.18.0-rc.1→next,1.18.0-canary.5→canary.Remaining ops
The backlog needs one of: push
npm-v1.17.1to publish the current stable (the final was never published to npm — only rc.1), or a one-offnpm dist-tag add reasonix@<current stable> latest. After that, this workflow keepslatesthonest on every future stable. Consider alsonpm deprecate reasonix@"<1.0.0"so remaining 0.x users get a heads-up.Refs #5822