Skip to content

Suggestion: Node.js 27 Alpha shared tags #2698

Open

Description

@MikeMcC399

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.

Currently

(from https://github.com/docker-library/official-images/blob/master/library/node)

Tags: 27.0.0-alpha.0.1.0-alpine3.23
Architectures: amd64, arm64v8

Tags: 27.0.0-alpha.0.1.0-alpine3.24
Architectures: amd64, arm64v8

Tags: 27.0.0-alpha.0.1.0-bookworm
Architectures: amd64, arm64v8, ppc64le

Tags: 27.0.0-alpha.0.1.0-bookworm-slim
Architectures: amd64, arm64v8, ppc64le

Tags: 27.0.0-alpha.0.1.0-trixie
Architectures: amd64, arm64v8, ppc64le, s390x

Tags: 27.0.0-alpha.0.1.0-trixie-slim
Architectures: amd64, arm64v8, ppc64le, s390x

Suggested change

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

Tags: 27.0.0-alpha.0.1.0-alpine3.23 27-alpha-alpine3.23
Architectures: amd64, arm64v8

Tags: 27.0.0-alpha.0.1.0-alpine3.24 27-alpha-alpine3.24 27-alpha-alpine
Architectures: amd64, arm64v8

Tags: 27.0.0-alpha.0.1.0-bookworm 27-alpha-bookworm 
Architectures: amd64, arm64v8, ppc64le

Tags: 27.0.0-alpha.0.1.0-bookworm-slim 27-alpha-bookworm-slim
Architectures: amd64, arm64v8, ppc64le

Tags: 27.0.0-alpha.0.1.0-trixie 27-alpha-trixie 27-alpha
Architectures: amd64, arm64v8, ppc64le, s390x

Tags: 27.0.0-alpha.0.1.0-trixie-slim 27-alpha-trixie-slim 27-alpha-slim
Architectures: amd64, arm64v8, ppc64le, s390x

Activity

  1. MikeMcC399 commented on Nov 16, 2026

    @MikeMcC399
    MemberAuthor

    Considerations

    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.

  2. nschonni commented on Nov 16, 2026

    @nschonni
    Member

    Related thought #2681 (comment)

    note sure if some of the other combos of floating variants should also be added like:

    • alpha for the default Debian
    • alpha-slim for the default Debian-slim
    • alpha-alpine for whatever is the default Alpine during the Alpha
      Could skip the various alpha-trixie, etc though
  3. MikeMcC399 commented on Nov 16, 2026

    @MikeMcC399
    MemberAuthor

    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.

  4. MikeMcC399 commented on Nov 17, 2026

    @MikeMcC399
    MemberAuthor

    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:

    Documentation: https://nodejs.org/docs/v27.0.0-alpha.0.1.1/api/

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions