Skip to content

[release/9.0-staging] Map version for Tahoe compatibility. #116641

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

Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jun 13, 2025

Backport of #116536 to release/9.0-staging

/cc @akoeplinger @vcsjones

Customer Impact

  • Customer reported
  • Found internally

macOS Tahoe returns a compatibility version, 16, for macOS 26 unless it is built with Xcode 26's SDK.

Since we're relying on Azure Pipelines macOS images and don't control when they bump to the new Xcode SDK we could have a period of time when e.g. Environment.OSVersion returns 16.0. This also impacts checks like OperatingSystem.IsMacOSVersionAtLeast(26).

To address this we remap the version from 16 to 26, just like we did the last time when Apple changed the versioning in macOS Big Sur.

Regression

  • Yes
  • No

No, this is caused by changes in Apple's newest OS release.

Testing

Manual testing.

Risk

Low. This just remaps a version number that would be returned on the new macOS release.

macOS Tahoe returns a compatibility version, 16, for macOS 26 unless it is built with Xcode 26's SDK.
As we did with Big Sur, this maps the compatibility version 16 to 26.

The intention is that we will be on the new SDK by the time macOS 27 rolls out. If not, then we will need to add another compatibility map, most likely.
It does not appear that iOS, tvOS, or Catalyst return compatibility numbers, so they are excluded from doing any mapping.
@akoeplinger akoeplinger added this to the 9.0.x milestone Jun 13, 2025
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-system-runtime
See info in area-owners.md if you want to be subscribed.

@rbhanda rbhanda modified the milestones: 9.0.x, 9.0.8 Jun 26, 2025
@rbhanda rbhanda added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Jun 26, 2025
@akoeplinger
Copy link
Member

/ba-g unrelated wasm timeout

@akoeplinger akoeplinger merged commit f377282 into release/9.0-staging Jul 1, 2025
91 of 100 checks passed
@akoeplinger akoeplinger deleted the backport/pr-116536-to-release/9.0-staging branch July 1, 2025 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants