Skip to content

doc: reorganize platform list#61569

Open
kleisauke wants to merge 5 commits intonodejs:mainfrom
kleisauke:alpine-versions
Open

doc: reorganize platform list#61569
kleisauke wants to merge 5 commits intonodejs:mainfrom
kleisauke:alpine-versions

Conversation

@kleisauke
Copy link

@kleisauke kleisauke commented Jan 28, 2026

See the individual commits for more details.

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/build
  • @nodejs/tsc

@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations. labels Jan 28, 2026
Copy link
Member

@sxa sxa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As a possible follow-up, we could also mention the musl-based Linux arm64 binaries

+1 to this since we're now building it so it's as experimental as some of the others in the table.

Commenting as opposed to approving/rejecting as I'd like to see the arm64 change in but I won't block if you want to do it separately :-)

@kleisauke
Copy link
Author

@sxa I just opened PR #61589 to include the musl-based Linux arm64 binaries into the platform list.

@legendecas
Copy link
Member

Is https://github.com/nodejs/unofficial-builds/blob/main/recipes/musl/Dockerfile used for every active release lines (v20.x, v22.x, v24.x, v25.x)?

@kleisauke
Copy link
Author

Is https://github.com/nodejs/unofficial-builds/blob/main/recipes/musl/Dockerfile used for every active release lines (v20.x, v22.x, v24.x, v25.x)?

I believe so. Given that commit nodejs/unofficial-builds@d8eaee5 landed on May 6, 2024, the binaries built with Alpine 3.19 likely correspond to the version range: ^20.13.0 || ^22.2.0 || >=24.0.0.

@richardlau
Copy link
Member

This part of the doc doesn't refer to compatibility of the unofficial binaries -- it is supposed to indicate compatibility in general for that platform (e.g. building from source yourself). They are most likely best guesses because I don't think anyone has tried to extensively test Node.js against kernel versions.

The requirements to run the official binaries are in the "Official binary platforms and toolchains" section. There is no section for unofficial builds, and I would block any addition/mention of unofficial builds to BUILDING.md (as unofficial builds are unofficial).

@kleisauke kleisauke changed the title doc: update kernel and musl reqs for Alpine doc: reorganize platform list Mar 2, 2026
BUILDING.md Outdated
Comment on lines +165 to +167
[^5]: Older kernel or libc versions may work. The minimum versions listed here
correspond to the binaries provided by the
[unofficial-builds project](https://github.com/nodejs/unofficial-builds).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm -1 on mentioning unofficial-builds in this document. We do not want people relying on them.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Understood. The mention has been removed.

@richardlau richardlau added dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. dont-land-on-v24.x PRs that should not land on the v24.x-staging branch and should not be released in v24.x. labels Mar 2, 2026
@richardlau richardlau added the dont-land-on-v25.x PRs that should not land on the v25.x-staging branch and should not be released in v25.x. label Mar 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations. dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. dont-land-on-v24.x PRs that should not land on the v24.x-staging branch and should not be released in v24.x. dont-land-on-v25.x PRs that should not land on the v25.x-staging branch and should not be released in v25.x.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants