You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 28c23c0
Browse filesBrowse the repository at this point in the historyBrowse files
fix: latest never moves backward on a re-run; pack:verify builds from a clean dist
- publish-npm chooses the dist-tag at publish time: latest for the move from
the date-stamped line to 1.x and for a version higher than the registry's
latest, backfill otherwise. An older release's failed leg re-run after a
newer version published no longer drags latest back.
- pack:verify removes dist before packing. tsc never deletes the output of a
removed or renamed source file, so a previously built checkout could pack
files a fresh checkout would not.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Signed-off-by: cliffhall <[email protected]>
Copy file name to clipboardExpand all lines: RELEASING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Semver policy:
22
22
|**minor**| A new tool, prompt, resource or option |
23
23
|**major**| A breaking change: a tool removed or renamed, a schema change that breaks clients, a protocol or Node floor bump |
24
24
25
-
The semver line starts at **`1.0.0`** for all four packages. Their earlier releases were date-stamped (`2025.x`, `2026.x`), which sorts above any semver number, but `npm install` and `npx` resolve the `latest` dist-tag rather than the highest number, so publishing `1.x` is what users get. npm will not move `latest` to a lower version implicitly, so `release.yml`publishes with an explicit `--tag latest`. Once `1.0.0` is live, a scope maintainer deprecates the date-stamped range (`>=2025.0.0 <2027.0.0`) by hand, once; the `release` skill has the command and the check to run first.
25
+
The semver line starts at **`1.0.0`** for all four packages. Their earlier releases were date-stamped (`2025.x`, `2026.x`), which sorts above any semver number, but `npm install` and `npx` resolve the `latest` dist-tag rather than the highest number, so publishing `1.x` is what users get. npm will not move `latest` to a lower version implicitly, so `release.yml`always passes the dist-tag explicitly, and chooses it at publish time: `latest` for the move from the date-stamped line to `1.x` and for any version higher than the registry's current `latest`, and `backfill` otherwise. The second case is an older release's failed leg re-run after a newer version has published: the version becomes installable by number, and `latest` does not move backward. Once `1.0.0` is live, a scope maintainer deprecates the date-stamped range (`>=2025.0.0 <2027.0.0`) by hand, once; the `release` skill has the command and the check to run first.
0 commit comments