You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently publishing Node.js 27 Alpha images with only simple (pinned) tags
This is a suggestion for shared (floating) tags which I think ties in with previously thinking. Once Node.js 27 reaches the Current phase and drops the pre-release -alpha.0.0.0 from the semver tag, it should be treated the same as previous non-prerelease versions.
There is no plan for Node.js releasing anything other than 27.0.0-alpha.x.x.x during the Alpha phase. There is no 27.1.0-alpha.x.x.x for example planned.
Don't create shared tags for the alpha.x.x.x part.
Use only 27-alpha alpine3.24 default for alpine (until Alpine Linux 3.25 is released, possibly in Dec 2026, then it gets bumped) trixie default for no os and for slim
Users shouldn't accidently pull an Alpha version if they thought they were getting non-prelease. Using 27-alpha is good for that. Trying to pull 27 on its own during the Alpha phase would deliberately fail.
I submitted nodejs/nodejs.org#9334 to first of all use simple (pinned) versions for Node.js 27 Alpha Docker images on the https://nodejs.org/en/download/alpha page as a first pass to make it work at all. This could be easily adapted to use instead the shared (floating) tag 27-alpha.
The problem with adding alpha without 27 is that this is something that expires and gets stuck without being obvious. If it's always 27-alpha, then it's clear that it's tied to 27. If you want the next Alpha a year later, you'd need to select that again explicitly 28-alpha.
This is how actions/setup-node handles nightlies, you always have to specify the version as well 28-nightly is the current one.
I'd be happy with the suggestion, however I am not in a hurry to implement it and I would be equally OK with waiting to see how tagging / directory naming etc. develops in general during the 6 month Alpha period.
Activity
MikeMcC399 commentedon Nov 16, 2026
Considerations
Users shouldn't accidently pull an Alpha version if they thought they were getting non-prelease. Using
27-alphais good for that. Trying to pull27on its own during the Alpha phase would deliberately fail.I submitted nodejs/nodejs.org#9334 to first of all use simple (pinned) versions for Node.js 27 Alpha Docker images on the https://nodejs.org/en/download/alpha page as a first pass to make it work at all. This could be easily adapted to use instead the shared (floating) tag
27-alpha.nschonni commentedon Nov 16, 2026
Related thought #2681 (comment)
MikeMcC399 commentedon Nov 16, 2026
The problem with adding
alphawithout27is that this is something that expires and gets stuck without being obvious. If it's always27-alpha, then it's clear that it's tied to 27. If you want the next Alpha a year later, you'd need to select that again explicitly28-alpha.This is how
actions/setup-nodehandles nightlies, you always have to specify the version as well28-nightlyis the current one.MikeMcC399 commentedon Nov 17, 2026
I'd be happy with the suggestion, however I am not in a hurry to implement it and I would be equally OK with waiting to see how tagging / directory naming etc. develops in general during the 6 month Alpha period.
Right now there's still no generic place to find the API documentation, and you need to follow https://nodejs.org/en/blog/release/v27.0.0-alpha.0.1.1 to find the pinned link: