[2025] DevOps Annual Deprecation Cycle

Unity DevOps Build Automation is dedicated to delivering optimal user experience for our customers. To achieve this goal, we must consistently assess and refresh the dependencies necessary for successfully building your projects. Although prioritizing the integration of new dependencies is essential, we also recognize the importance of phasing out unsupported or outdated ones.

What’s happening?

We have three updates to share today:

  1. Operating System Support and Availability
  2. Xcode Support and Availability
  3. Unity Support and Availability

We will cover the Support and Availability of each below.

Operating System Support and Availability

To improve the similarity between your local desktop and the build machines while building projects for Unity, we will be removing support for some of our older Operating System versions.

The following Operating System will be removed on April 30th, 2025. Any Build Targets using these operating systems will be automatically migrated to macOS Ventura - Silicon. In addition, starting April 14th 2025, no new Unity versions will be made available, and the option to always use a latest version of Unity will be removed for these Operating System versions.

  • macOS Ventura (Intel)

The following Operating Systems will be deprecated on April 14th, 2025, and removed on June 17, 2025. Any Build Targets using these operating systems at the time of removal will be disabled automatically.

  • macOS Ventura - Silicon

The following Operating Systems will remain enabled

  • Windows 11
  • macOS Sonoma - Silicon

Xcode Support and Availability

To align with the upcoming requirements regarding Xcode from Apple, we are going to deprecate all Xcode versions below Xcode 16, with an exception for Xcode 15.4.0.

The following Xcode Versions will be deprecated on April 14th, 2025, and removed on June 17, 2025. Any Build Targets using these Xcode versions at the time of removal will be automatically disabled.

  • Xcode 15.3.0
  • Xcode 15.2.0
  • Xcode 15.1.0
  • Xcode 15.0.0
  • Xcode 14.3.1

The following Xcode Versions will remain enabled

  • Xcode 15.4.0
  • Xcode 16.0.0
  • Xcode 16.1.0
  • Xcode 16.2.0

Please refer to this Xcode compatibility lookup page to see the upcoming changes to Unity and Xcode versions supported on Mac hardware. For additional questions, please visit the DevOps Build Automation Discussions Page.

Unity version Support and Availability

We are deprecating older Unity versions in line with our long-term-support (LTS) policy.

The following Unity Versions will be marked as deprecated on April 14, 2025, and will be removed on June 17th, 2025. Any Build Targets using these Unity versions at the time of removal will be automatically disabled.

  • 6000.0 Beta
  • 2023.3 Beta
  • 2023.2.x
  • 2023.1.x
  • 2022.2.x
  • 2022.1.x

The following Unity Versions will remain enabled:

  • 6000.1 Beta
  • 6000.0.x
  • 2022.3.x
  • 2021.3.x
  • 2020.3.48f1
  • 2019.4.40f1

If you would like us to make an exception for you, please reach out via a support ticket and share the details with us there.

What do you need to do?

We encourage you to update your project’s Unity and Xcode versions along with the Builder Operating System to compatible selections (see above) before the corresponding dates to ensure business continuity. Starting April 14th, 2025, deprecated dependencies will be marked with a “deprecated” label to differentiate them from supported and accessible dependencies. These dependencies will then be removed from the system on June 17, 2025.

3 Likes

Hey there! We’re in the process of updating (from Ventura Intel+Xcode 15) according to this deprecation and to comply with iOS store requiring iOS 18, and thus Xcode 16 starting the end of the April. But we have the issue that every 2nd build fails with Sonoma Silicon+Xcode 16+Unity 6000.0+ECS.

Specifically the build errors look like this:
Error building Player: Exception: Building EntityScene artifact failed: 'Assets/.../Scenes/MainGameSceneEntities.unity' ([some guid]). There were exceptions during the entity scene imports

Can we count with builds being more stable by the time the architectures get deprecated?

Hi Diego - our internal suite of tests using these latest configuration options has been stable for awhile now, so this might be something specific to your project. I would recommend filing a support ticket so that one of our engineers can help you investigate this.

You can file a ticket by clicking the “Help and Support” button at the bottom of the left column of the DevOps Dashboard, and then clicking the “File Ticket” option at the bottom of that page.

1 Like

I’m having trouble using the Google Cloud CLI with the new builders (Windows 11 mainly).

When I try to run commands like: gcloud storage cp "$BUILD_PATH" "gs://$BUCKET/..." -r --cache-control=no-store. I have the following internal CLI error: [error] ERROR: gcloud crashed (ValueError): too many values to unpack (expected 4)

This used to work fine on macOS Ventura (Intel). We are unable to migrate due to this error. Do you have any similar reports?

That sounds like it might be caused by the newer OS Images having an updated version of some gcloud dependency, although it’s difficult to say for sure. I’d recommend contacting support so they can dig into this issue a bit deeper.

Are you able to build on Ventura Silicon or Sonoma in the mean time?

I’ve just tested it. It works fine with Sonoma - Sillicon. It didn’t work on Windows 11. Should I create a ticket to report it? Or can you handle it internally?

Thank you for your advice.

We’ll probably need to go into a little more detail as to how exactly you’re using gcloud and what the rest of your script look like. This Discussions post probably isn’t the best place for that sort of back-and-forth, so I’d recommend still submitting a ticket

1 Like

Hey Folks, In order to avoid making drastic changes on a Friday, we’ll be delaying the removal of deprecated version to next Tuesday, June 17th. Thanks!