Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: increase MACOS_DEPLOYMENT_TARGET to 10.10 for Node 12 #27275

Closed
wants to merge 1 commit into from

Conversation

rvagg
Copy link
Member

@rvagg rvagg commented Apr 17, 2019

Ref: #26714
Ref: nodejs/build#1768

This is part of the Node 12 compiler & supported platforms work. It was last bumped in #6402 in 2016.

From #26714:

The trade-off goes something like this: users who are on a macOS older than this number won't be able to run our binaries, but by including support for old versions we locking ourselves into supporting header layouts that may not hold (the only instance of this that I recall happened only recently but I can't find the issue for it) and perhaps there's missed optimization opportunities by forcing binding to older APIs.

But I'll add that I'm not fully confident about this, I'm still hoping for help making this decision.

10.9 is Mavericks, it was released in 2013 and had its last security update mid-2016. This change will mean that 10.9 and prior versions won't be able to run Node binaries because they'll (probably) have newer symbols.

If, for some reason, we find that 10.10 is too aggressive, we can always roll this back a bit without it being a breaking change, we just can't roll it forward for the lifetime of Node 12.

@rvagg rvagg added the semver-major PRs that contain breaking changes and should be released in the next major version. label Apr 17, 2019
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot nodejs-github-bot added the build Issues and PRs related to build files or the CI. label Apr 17, 2019
@rvagg
Copy link
Member Author

rvagg commented Apr 17, 2019

@nodejs/build

@nodejs-github-bot
Copy link
Collaborator

Copy link
Member

@bnoordhuis bnoordhuis left a comment

Choose a reason for hiding this comment

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

LGTM but personally I'd go a step further and move up to 10.11 (El Capitan.) Apple stopped supporting 10.10 almost two years ago so why should we?

@refack
Copy link
Contributor

refack commented Apr 17, 2019

I like dropping some stats for making this kind of educated guesses
http://gs.statcounter.com/macos-version-market-share/desktop/worldwide/#monthly-201904-201904-bar
StatCounter-macos_version-ww-monthly-201904-201904-bar

@rvagg
Copy link
Member Author

rvagg commented Apr 18, 2019

Landed in a7d7d4d

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. semver-major PRs that contain breaking changes and should be released in the next major version.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants