-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Conversation
@nodejs/build |
There was a problem hiding this 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?
I like dropping some stats for making this kind of educated guesses |
Landed in a7d7d4d |
PR-URL: #27275 Refs: #26714 Refs: nodejs/build#1768 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
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:
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.