Repository navigation
Description
Currently the project builds three macOS packages available to download from nodejs.org:
- macOS arm64 tarball
- macOS x64 tarball
- macOS universal binary pkg (i.e. the same installer installs either arm64 or x64).
To build the pkg we build Node.js twice on an arm64 macOS VM:
- Once for x64 under Rosetta 2
- Once for arm64 (native)
and then combine the two into the pkg, sign/notarize.
Apple have announced that the last release of macOS that will support Rosetta 2 will be macOS 27. That's the version two on from what we're currently on (macOS 15 -- Apple renumbered so the sequence goes macOS 15, macOS 26, macOS 27). The same Apple announcement said that the last macOS version to support x64 is Tahoe (26).
So we have two decisions:
- At some point we make the pkg builds arm64 only (as we currently need Rosetta 2 to build those without significant rework of how the releases are done).
- At some point we will need to drop the x64 macOS version of Node.js completely.
Planning is a little difficult with macOS because Apple do not usually announce End-of-Life dates... they just stop releasing after a while. Also they have made changes before around signing/gatekeeper which forced Xcode updates that in turn forced macOS version updates. So there's a large element of "our best guess" when trying to work out what we're likely to be able to support for the duration of a Node.js release line.
Starting the discussion now as I think our preference would be to make changes on semver major boundaries (unless Apple forces our hand as with the previously mentioned signing/gatekeeper change). So discuss first wrt. Node.js 27 (2027) and if we decide that is too soon, switch focus to Node.js 28 etc.
Refs: nodejs/node#63055
Activity
sxa commentedon May 1, 2026
Summary of some points from the other issue:
sxa commentedon May 1, 2026
As another data point to give an idea of the relative use of the two architectures, another major language runtime (Eclipse Temurin by Adoptium) currently has around 8X more macos tarball/package downloads of the JDK on arm64 when compared with x64. For older releases like java 11 it's about 3X, although for the JRE instead of the JDK the numbers are much closer (in fact for java 11 the JRE has more x64 downloads than arm64). JRE/11 vs JDK/25 are shown in the charts below:
sxa commentedon May 1, 2026
See also nodejs/node#63055 (comment) which has some (interpret with caution!) stats from Cloudflare on our downloads.
aduh95 commentedon May 6, 2026
Is there any update here? We were discussing in the TSC meeting whether nodejs/node#63055 should land on 26 release line.
FWIW, user stats is hardly relevant here, we're not discussing downgrading support for a lack of usage, but rather because of a likely impossibility to produce binaries and get CI runners – assuming we require HomeBrew or Rosetta, but maybe I'm wrong here
sxa commentedon May 7, 2026
While I'm not disagreeing with the downgrade to tier 2 (I'm 100% in support of this as you know and I've approved the PR for 26) it's worth bearing a couple of things in mind based on how we build and test macos (currently exclusively in orka from macstadium). I think we should still at least be mindful of the stats/userbase at the time we chose to remove support for i:
rustfrom source, but hopefully we won't be doing any significant V8 upgrade to the supported releases after Homebrew stops supporting x64 towards the end of next year :-)One blocker could be if macstadium stopped being able to provide x64 hardware at some point, although we've demonstrated (via the iojs+release pkg build) that the releases can be cross-compiled with Rosetta on the arm64 systems, so we should have some security in that respect as long as we have macos27/arm64 systems available.
Also worth noting that since a significant proportion of downloads appear to come from MSFT/github actions. From this issue it looks like they will stop supporting x64 from around the same time as Homebrew so expect we'll see a significant drop off in use around that time:
To be clear, I'm absolutely not using any of this to say we shouldn't continue with the deprecation but it's worth having those detailed here for a common understanding of how the macos builds are currently built and released with the associated risks/mitigations for input to the discussion.
aduh95 commentedon May 7, 2026
Thanks for the detailed explanation!
To clarify, I meant "hardly relevant for Tier 2 on Node.js 26", I agree that for the upcoming major versions it is relevant.
ryanaslett commentedon May 26, 2026
I've reached out to MacStadium to ask if they have any concrete deprecation plans to drop intel support. The Mac Mini's we use were built in 2018. They wont be able to replace those as hardware starts failing. I'll update if I hear back from them.
MacStadium does not offer X64 support on Orka for macOS 26 (https://support.macstadium.com/hc/en-us/articles/28336509227419-Compatibility-Matrix). The most recent version of OSX we can run on intel will be macOS 15, which given Apple's regularity and now annualized numbering, means osx15 will be unsupported in Sep 2028. That gives us about a year of running "unsupported OS" to run x86 tests for the Node 2026 support cycle.
Homebrew is essentially demoting X64 to the Tier 3 graveyard in Sep 2026 (https://docs.brew.sh/Support-Tiers), Once that happens, we're pretty much stuck with whatever images we happen to be running, and any changes to those images have to be hand massaged to make happen. That makes me really nervous to have to manually compile everything from source that we might need to update in order to test on x64. One year on the last year of a supported version isn't terrible, because most of the updates and changes are usually minimal, platform wise.
If we lose x64 hardware, then I think support has to be dropped to experimental, correct? i.e. if we cant test, then we cant know about broken tests etc.
doc: downgrade macOS x64 to Tier 2
ryanaslett commentedon Jun 15, 2026
I've received a response from MacStadium with the following information:
So given that, I think we should not extend x86 support beyond December 2027. I certainly do not want to put any platform engineering effort into getting a replacement in place and working so that very old, very unsupported osx laptops can keep using Node.
aduh95 commentedon Jun 15, 2026
Thanks for inquiring!
For reference, Node.js 24 EOL is scheduled for 2028-04-30, hopefully we can keep the machines until then. For Node.js 26 (EOL scheduled for 2029-04-30), we probably need to document that Tier 2 support won't be available as of early 2028.
richardlau commentedon Aug 20, 2026
nodejs/node#65427 proposes stopping producing macOS x64 binaries from Node.js 27 onwards. Noting here that would involve both
VersionSelectorScript.groovychanges (for the tarballs) and nodej/node Makefile changes (pkg builds).aduh95 commentedon Sep 16, 2026
I've opened #4470
I've added nodejs/node@b9a43a8 to nodejs/node#65427 to address that
macos: drop x64 macOS tarball from release matrix (#4470)
build: downgrade Intel macOS support to experimental
Revert "build: update Makefile to support fat binary"