[3.x] Publish releases under the legacy dist-tag - #444
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
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.
Stable versions published from this branch currently go to npm as latest, because the dist-tag is resolved purely from the prerelease suffix. The latest tag points at 4.1.0 today only because it happened to be published after 3.77.0 on the same day; the next 3.x release would steal it and make npm install osls serve 3.x. This maps stable 3.x versions to the legacy dist-tag instead, leaving the prerelease mappings unchanged. Release workflows run from the definition at the tagged commit, so this change on the 3.x branch is sufficient and the 4.x branch needs nothing.