docs(release): document the legacy dist-tag move and fix the post-release bump step - #1443
Merged
Conversation
msluszniak
added a commit
that referenced
this pull request
Sep 8, 2026
msluszniak
changed the title
barhanc
approved these changes
Sep 8, 2026
msluszniak
added a commit
that referenced
this pull request
Sep 8, 2026
Post-release bump for the 0.11 development cycle (RELEASE.md step 10), now that v0.10.0 is on npm. | Change | Detail | | --- | --- | | `version` in all four published packages | 0.10.0 -> 0.11.0 | | `LIB_VERSION` in `telemetry.ts` | 0.10.0 -> 0.11.0 | | `models.ts` | `NEXT_VERSION_TAG` renamed to `VERSION_TAG`, value stays `resolve/v0.10.0`, rewriting all 288 model URLs | | `nativeLibsVersion` | left at 0.10.0 on purpose; `v0.11.0-libs` does not exist yet | Typecheck clean, 3842 tests pass, and 4 sampled model URLs return 200 on HuggingFace. The step as documented did not build, since it left `NEXT_VERSION_TAG` with no reader. The RELEASE.md correction lives in #1443 to keep this PR code-only.
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.
Two gaps in RELEASE.md, both found while running the 0.10.0 release.
The
legacydist-tag was never documentedNothing told you to move it after a release, which is why it sat on 0.8.5 through the whole 0.9 line and the satellites were still on 0.8.0. The automation will not do it: the publish action only derives
latestfor the newest version orlegacyfor an older one, and when it pickslegacyit runsnpm dist-tag rm <pkg> legacyright after publishing.Added as step 9, plus a note that a patch on an older line ends with no
legacytag and needs it re-added.The post-release bump step did not build
Step 10 said to add
VERSION_TAGback and setNEXT_VERSION_TAGto the next cycle. Once every URL moves toVERSION_TAGnothing readsNEXT_VERSION_TAG, andnoUnusedLocalsrejects it. Same failure #1442 hit from the other direction.Reworded to: exactly one of the two constants exists at a time, the rename does the URL rewrite by construction, and
NEXT_VERSION_TAGreturns with the first model re-exported next cycle. Also corrected "both adapter packages" to all four, and flagged thatnativeLibsVersionmust not be bumped there.Steps 9-14 renumbered to 10-15. Docs only.