Skip to content

How to handled musl x64 becoming "official"/Tier 2 #247

Open

Description

@nschonni

No urgency or need for change, but thinking about what might need to change in this repo if nodejs/node#63737 lands.

Possible Option:

  1. Do nothing, keep building here, even when the official builds start being produced
  2. Turn off builds, or limit the version if the Tier 2 only starts in future releases
  3. Keep serving them from this dist, but just rsync/copy the offial ones and a merged SHASUMS.txt

I don't think the musl/arm64 is on the table for Tier 2 right now, so that build would probably continue anyway.

/cc @sxa

Activity

  1. rvagg commented on Jul 31, 2026

    @rvagg
    Member

    Lovely; my inclination would be to have some small period of overlap and then phase out and stop building here. Any idea if the current process of upgrading it to official would involve pushing out builds for all the active release lines or would we need to deal with older release lines here and only get official ones for the most recent line?

  2. MikeMcC399 commented on Nov 2, 2026

    @MikeMcC399
    Contributor

    nodejs/node#63737 landed on Sep 24, 2026 with nodejs/node@bcf5850

    In the meantime, Node.js Docker images for each of the supported release lines have been published based on official Tier 2 musl images.

    Node.js Docker Tier 2 musl since PR
    26.x 26.11.0 nodejs/docker-node#2647
    24.x 24.22.0 nodejs/docker-node#2652
    22.x 22.23.4 nodejs/docker-node#2662

    https://github.com/nodejs/docker-node no longer depends on unofficial musl builds from this repo.

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