Skip to content

doc: announce upcoming end of tier 2 support for macOS x64#63931

Open
aduh95 wants to merge 1 commit into
nodejs:mainfrom
aduh95:x86_64-darwin-eol
Open

doc: announce upcoming end of tier 2 support for macOS x64#63931
aduh95 wants to merge 1 commit into
nodejs:mainfrom
aduh95:x86_64-darwin-eol

Conversation

@aduh95

@aduh95 aduh95 commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

The timeline will hopefully be (unfortunately order is not guaranteed):

  1. 2028-04-30: Node.js 24 EOL (Node.js 24 lists macOS x64 as Tier 1)
  2. Early 2028: MacStadium end of support for our testing infra
  3. 2029-04-30: Node.js 26 EOL (Node.js 26 lists macOS x64 as Tier 2)
  4. 2029: Apple end of support for our building infra1

Refs: nodejs/build#4317 (comment)

Footnotes

  1. https://developer.apple.com/documentation/apple-silicon/about-the-rosetta-translation-environment/ announced that macOS 27 will be the last version with full Rosetta 2 support, which we use to build the universal binaries. macOS 27 EOL is unknown, based on previous version we should expect it to last until 2029 (and can get away with running it post its EOL as those machines only run trusted code).

@aduh95 aduh95 added 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 Jun 15, 2026
@nodejs-github-bot

Copy link
Copy Markdown
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 Jun 15, 2026
Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
@aduh95 aduh95 force-pushed the x86_64-darwin-eol branch from 6f72fb4 to 735b376 Compare June 15, 2026 16:30
@richardlau

Copy link
Copy Markdown
Member

FWIW this isn't really an announcement -- I don't think people in general will notice this change unless attention is brought to it (either they are looking when upgrading from older versions or someone has pointed them at it).

@mcollina mcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

lgtm, we should also include a blog post.

Note that by this timeline we would have 2 years for Node 26 without the testing infrastructure.

I don't think this is tenable, so we'd have to lower it in flight for Node 26.

@aduh95

aduh95 commented Jun 16, 2026

Copy link
Copy Markdown
Contributor Author

@mcollina only one year. This PR goal is to document that macOS x64 will be de facto experimental as of early 2028.

@Renegade334 Renegade334 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

+1 for a blog post.

@sxa sxa left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can I just clarify something before this is approved:

will no longer be able to test changes on any Intel-based macOS version, so the only difference with Experimental tier is that the project intends to keep creating universal binaries, compatible with both Apple Silicon-based and Intel-based macOS versions.

Is the intention here that we would be shipping the universal binaries after MacStadium shuts down the x64 hardware meaning that the x64 side would be completely untested despite being distributed through the formal channels?

In reality "The only difference" is therefore that it is completely untested and not in any way guaranteed to work in any capacity - is that correct? If so I'm not sure "The only difference" in the current sentence specifies any difference ... Either that or I'm typing this so late that I've missed something obvious but I'm going to "request changes" to stop this being merged until that is clarified :-)

(Also noting that we would technically have the option to test under Rosetta on arm hardware for a little longer while that is available if desired)

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.