fix(export): use managed stable version when rc dist-tag is stale (#407)#409
Open
Yonkoo11 wants to merge 1 commit into
Open
fix(export): use managed stable version when rc dist-tag is stale (#407)#409Yonkoo11 wants to merge 1 commit into
Yonkoo11 wants to merge 1 commit into
Conversation
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.
Closes #407
When
versions.tsholds a stable semver (e.g.2.3.0) and no RC snapshot exists, staging exports were falling back to the barercnpm dist-tag. That tag currently resolves to2.0.0-rc.1(April 2026), which predates features shipped in stable releases — most visibly ENS name resolution (landed in2.1.0→2.3.0).Fix: When no RC version is available, staging now uses the managed stable version directly (with
^prefix), matching the behavior of UI packages. This ensures staging exports always ship with the features documented inversions.ts.Production exports are unaffected — they already pin
^<managedVersion>.