Skip to content

[EXEC-5670] Update Xcode release & deprecation policy #9529

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

OompahLoompah
Copy link
Member

Description

Update the Xcode release & deprecation policy with the new deprecation policy and ensure the rest of the document is consistent with current practices.

Reasons

Current practice with regards to Xcode image release and deprecation diverged from our policy, especially regarding how we announce new images.

Content Checklist

Please follow our style when contributing to CircleCI docs. Our style guide is here: https://circleci.com/docs/style/style-guide-overview.

Please take a moment to check through the following items when submitting your PR (this is just a guide so will not be relevant for all PRs):

  • Break up walls of text by adding paragraph breaks.
  • Consider if the content could benefit from more structure, such as lists or tables, to make it easier to consume.
  • Keep the title between 20 and 70 characters.
  • Consider whether the content would benefit from more subsections (h2-h6 headings) to make it easier to consume.
  • Check all headings h1-h6 are in sentence case (only first letter is capitalized).
  • Include relevant backlinks to other CircleCI docs/pages.

@OompahLoompah OompahLoompah requested review from a team as code owners August 20, 2025 16:45
@OompahLoompah OompahLoompah changed the title Update Xcode release & deprecation policy [EXEC-5670] Update Xcode release & deprecation policy Aug 20, 2025
@OompahLoompah OompahLoompah force-pushed the EXEC-5670/update-xcode-deprecation-policy branch 2 times, most recently from 1141aae to dd68f01 Compare August 21, 2025 14:44

When a new major version of macOS (ex: `12.0`) is released, we will start to use this version after a minimum of two minor Xcode releases have passed. This will allow for any major bugs and issues to be resolved. Release timing for this is entirely dependent on Apple's own release cycle, but will always be announced on our link:https://discuss.circleci.com/c/announcements/39[Discuss forum].
When a new major version of macOS (ex: `12.0`) is released, we will start to use this version after a minimum of two minor Xcode releases have passed.
Copy link
Member

Choose a reason for hiding this comment

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

We might as well modernize this to "26.0", no?

Update the Xcode release & deprecation policy with the new deprecation policy and ensure the rest of the document is consistent with current practices.
Make the documentation's examples more relevant to modern times by updating the version number used in examples.
@OompahLoompah OompahLoompah force-pushed the EXEC-5670/update-xcode-deprecation-policy branch from 6286796 to d5b7a15 Compare August 22, 2025 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants