Repository navigation
chore: publish v13 releases under npm tag 'v13' instead of 'latest' - #2889
Merged
Merged
Conversation
gyaneshgouraw
approved these changes
Oct 14, 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
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.
Fixes the npm dist-tag used when publishing from the v13 release line.
Previously, stable v13 releases were published with
--tag latest, which overwrote thelatesttag on npmjs.com — causingnpm install auth0-lockto resolve to a v13 backport release instead of the current v15.Change:
TAG="latest"→TAG="v13"in the else branch ofaction.yml.After this, users can install the latest v13 release explicitly with:
While
npm install auth0-lockcontinues to resolve to the current v15 line.