Add support for alpha versions of node - #850
Draft
shadowspawn wants to merge 5 commits into
Draft
Conversation
- current should ignore alpha - beef up local sorting to get releases after prerelease - support offline install of alpha version - deprecate lts_latest
Collaborator
Author
|
Node.js is going with triple alpha numbers so can show semver major changes. First release going to be 27.0.0-alpha.0.0.0. |
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.
See #847 for more background and discussion.
Problem
Node.js is switching to yearly releases, with alpha -> current -> lts
What do we do with labels to support new policy?
Solution
Keep using
latestandcurrentlabels, with refined behaviour forcurrent:latest: newest releasecurrent: newest release ignoring alpha versionsNode.js will have periods when there is not a version in its "current" phase. We just match our
currentlabel to newest non-alpha, so may actually be in current or LTS phase. This seems more useful than being pedantic and returning an error.Add some extra handling for:
currentRemove
lts_latestfrom README.ChangeLog