Never publish v3 as latest on npm
#19043
Merged
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
Just `3` or `v3` are not valid and you will get an error. Angular uses
`v{n}-lts` for the versions they still support: https://www.npmjs.com/package/@angular/core?activeTab=versions
Adding a tag is important, because omitting the `--tag` is the same as
`--tag latest`
thecrypticace
approved these changes
Oct 1, 2025
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.
This PR ensures that if we release v3 in the future, that we don't use
latestas the npm tag, butv3-ltsinstead.Unfortunately we can't just use
3orv3because they are not valid and you will get an error when trying to publish.Angular uses
v{n}-ltsfor the versions they still support: https://www.npmjs.com/package/@angular/core?activeTab=versionsAdding a tag is important, because omitting the
--tagis the same as--tag latest