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

Bump minimum supported macOS versions to 10.13 #17451

Closed

Conversation

illicitonion
Copy link
Contributor

As per https://developer.apple.com/support/xcode/ Xcode from 14.0 no longer supports targeting 10.9, and attempting to do so may fail in obscure ways.

10.13 is still 5+ years old, so we retain coverage for a reasonable range on macOS versions.

@sgowroji sgowroji added team-Rules-ObjC Issues for Objective-C maintainers awaiting-review PR is awaiting review from an assigned reviewer labels Feb 9, 2023
@keith
Copy link
Member

keith commented Feb 12, 2023

just to verify this doesn't produce any new build warnings for deprecated APIs or anything right? also note that these binaries even with this will likely still run on older versions, they just might crash depending on macOS changes, so these values don't matter that much

@illicitonion
Copy link
Contributor Author

just to verify this doesn't produce any new build warnings for deprecated APIs or anything right?

Yes, I've built all of the files built with the affected codepaths and there were no warnings (or errors).

As per https://developer.apple.com/support/xcode/ Xcode from 14.0 no
longer supports targeting 10.9, and attempting to do so may fail in
obscure ways.

10.13 is still 5+ years old, so we retain coverage for a reasonable
range on macOS versions.
keith added a commit to bazelbuild/apple_support that referenced this pull request Feb 13, 2023
keith added a commit to bazelbuild/apple_support that referenced this pull request Feb 13, 2023
@illicitonion illicitonion deleted the min-macos-version branch February 23, 2023 13:46
@illicitonion
Copy link
Contributor Author

@bazel-io flag

@bazel-io bazel-io added the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Feb 23, 2023
@ShreeM01
Copy link
Contributor

@bazel-io fork 6.1.0

@bazel-io bazel-io removed the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Feb 23, 2023
meteorcloudy pushed a commit that referenced this pull request Feb 24, 2023
As per https://developer.apple.com/support/xcode/ Xcode from 14.0 no longer supports targeting 10.9, and attempting to do so may fail in obscure ways.

10.13 is still 5+ years old, so we retain coverage for a reasonable range on macOS versions.

Closes #17451.

PiperOrigin-RevId: 511577111
Change-Id: I770ff101f52d16f2fc402f054579740b650986cc

Co-authored-by: Daniel Wagner-Hall <dwagnerhall@apple.com>
ShreeM01 pushed a commit to ShreeM01/bazel that referenced this pull request Apr 4, 2023
As per https://developer.apple.com/support/xcode/ Xcode from 14.0 no longer supports targeting 10.9, and attempting to do so may fail in obscure ways.

10.13 is still 5+ years old, so we retain coverage for a reasonable range on macOS versions.

Closes bazelbuild#17451.

PiperOrigin-RevId: 511577111
Change-Id: I770ff101f52d16f2fc402f054579740b650986cc
keertk pushed a commit that referenced this pull request Apr 5, 2023
* Bump minimum supported macOS versions to 10.13

As per https://developer.apple.com/support/xcode/ Xcode from 14.0 no longer supports targeting 10.9, and attempting to do so may fail in obscure ways.

10.13 is still 5+ years old, so we retain coverage for a reasonable range on macOS versions.

Closes #17451.

PiperOrigin-RevId: 511577111
Change-Id: I770ff101f52d16f2fc402f054579740b650986cc

* Update BUILD.bazel

* Revert change

---------

Co-authored-by: Daniel Wagner-Hall <dwagnerhall@apple.com>
@keertk
Copy link
Member

keertk commented Apr 11, 2023

@bazel-io fork 4.2.4

ShreeM01 pushed a commit to ShreeM01/bazel that referenced this pull request Apr 11, 2023
As per https://developer.apple.com/support/xcode/ Xcode from 14.0 no longer supports targeting 10.9, and attempting to do so may fail in obscure ways.

10.13 is still 5+ years old, so we retain coverage for a reasonable range on macOS versions.

Closes bazelbuild#17451.

PiperOrigin-RevId: 511577111
Change-Id: I770ff101f52d16f2fc402f054579740b650986cc
ShreeM01 pushed a commit to ShreeM01/bazel that referenced this pull request Apr 11, 2023
As per https://developer.apple.com/support/xcode/ Xcode from 14.0 no longer supports targeting 10.9, and attempting to do so may fail in obscure ways.

10.13 is still 5+ years old, so we retain coverage for a reasonable range on macOS versions.

Closes bazelbuild#17451.

PiperOrigin-RevId: 511577111
Change-Id: I770ff101f52d16f2fc402f054579740b650986cc
keertk added a commit that referenced this pull request Apr 12, 2023
* Bump minimum supported macOS versions to 10.13

As per https://developer.apple.com/support/xcode/ Xcode from 14.0 no longer supports targeting 10.9, and attempting to do so may fail in obscure ways.

10.13 is still 5+ years old, so we retain coverage for a reasonable range on macOS versions.

Closes #17451.

PiperOrigin-RevId: 511577111
Change-Id: I770ff101f52d16f2fc402f054579740b650986cc

---------

Co-authored-by: Daniel Wagner-Hall <dwagnerhall@apple.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-review PR is awaiting review from an assigned reviewer team-Rules-ObjC Issues for Objective-C maintainers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants