Skip to content

Handle Node.js alpha releases - #26

Open
richardlau wants to merge 1 commit into
nodejs:mainfrom
richardlau:linkalphas
Open

richardlau wants to merge 1 commit into
nodejs:mainfrom
richardlau:linkalphas

Conversation

@richardlau

Copy link
Copy Markdown
Member

Create latest-vN.x links for Node.js alpha releases. Do not link latest to alpha releases.

Fixes: #24


There's still some debate on whether latest should point to the alphas. At the moment (without any changes) latest is not pointing at the v27.0.0-alpha.0.0.0 release, 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

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>
@rvagg

rvagg commented Nov 6, 2026

Copy link
Copy Markdown
Member

There's still some debate on whether latest should point to the alphas

I'm surprised that this hasn't been figured out yet as part of the switch! I was also surprised to find that current in the standard Node.js github actions resolved to v27, I guess that's coming from nvm and that perhaps the ecosystem has decided this one for you already?

@richardlau

Copy link
Copy Markdown
Member Author

There's still some debate on whether latest should point to the alphas

I'm surprised that this hasn't been figured out yet as part of the switch! I was also surprised to find that current in the standard Node.js github actions resolved to v27, I guess that's coming from nvm and that perhaps the ecosystem has decided this one for you already?

and a suggestion to have a separate next link:

@MikeMcC399

Copy link
Copy Markdown

@rvagg

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 latest.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Missing latest-v27.x in https://nodejs.org/download/release

3 participants