Repository navigation
Handle Node.js alpha releases - #26
richardlau wants to merge 1 commit into
Conversation
Create `latest-vN.x` links for Node.js alpha releases. Do not link `latest` to alpha releases. Signed-off-by: Richard Lau <richard.lau@ibm.com>
I'm surprised that this hasn't been figured out yet as part of the switch! I was also surprised to find that |
and a suggestion to have a separate |
|
As also mentioned in nodejs/node#67224 (comment) The actions/setup-node team are addressing these related issues:
Although they may share alias names, they are not dependent on this PR. They make their own decision about what they term It makes the resolution of related issues more complex because each of the Node.js version managers is taking their own decisions about what aliases to use and how to interpret them. |
Create
latest-vN.xlinks for Node.js alpha releases. Do not linklatestto alpha releases.Fixes: #24
There's still some debate on whether
latestshould point to the alphas. At the moment (without any changes)latestis not pointing at thev27.0.0-alpha.0.0.0release, and this PR does not change that. We can PR further changes later if needed.Refs: #23
Refs: nodejs/node#67224
cc @nodejs/build @nodejs/releasers
FYI @nodejs/version-management