# Macos 26.4+ update

**URL:** <https://discuss.circleci.com/t/macos-26-4-update/54610>\
**Category:** CircleCI Images\
**Tags:** macos\
**Created:** [June 1, 2026, 3:38am UTC](https://discuss.circleci.com/t/macos-26-4-update/54610 "2026-06-01T03:38:58Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gigas002](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/gigas002/32/37008_2.png) [@Gigas002](https://discuss.circleci.com/u/Gigas002)\
**Post date:** [June 1, 2026, 3:38am UTC](https://discuss.circleci.com/t/macos-26-4-update/54610/1 "2026-06-01T03:38:58Z")

</div>

We’re using `.circleci/config.yaml` with `xcode: 26.4.0` and were expecting `macos` to be updated up to `26.4` or newer as well, but it still uses 26.3.1 even for `26.5`: [https://circle-macos-docs.s3.amazonaws.com/image-manifest/v18380/manifest.txt](https://circle-macos-docs.s3.amazonaws.com/image-manifest/v18380/manifest.txt)

The problem is, for flutter workflows, since macos 26.4 release, the rendering system have changed, and therefore all the goldens tests are failing. This issue is out of scope for flutter, and the only sane way to resolve is to update runner’s OS version: [Goldens images changed after upgrade to macOS 26.4 · Issue #184182 · flutter/flutter · GitHub](https://github.com/flutter/flutter/issues/184182)

We would like to either see the way to change the macos runner version, or bind the runner version with xcode version.

---

<div class="post-metadata">

**Author:** ![OliverNarramore](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/olivernarramore/32/36979_2.png) [@OliverNarramore](https://discuss.circleci.com/u/OliverNarramore)\
**Post date:** [June 4, 2026, 1:45pm UTC](https://discuss.circleci.com/t/macos-26-4-update/54610/2 "2026-06-04T13:45:51Z")

</div>

> [@Gigas002](#):
>
> Goldens images changed after upgrade to macOS 26.4 · Issue #184182 · flutter/flutter · GitHub

Our team are also blocked by this and have no means of rolling back our MacOS systems to 26.3. MacOS is now at version 26.5 and CircleCI is using 26.3.1… As a result, we have to push changes and wait for CI to generate/update the goldens, which adds significant turnaround time to what should normally be a fast local workflow.

This is starting to have a noticeable impact on development velocity and confidence in our test pipeline.

Others are impacted by this too ~ [Xcode 26.4.1 Released - #10 by OliverNarramore](https://discuss.circleci.com/t/xcode-26-4-1-released/54542/10)

Hopefully CircleCI can rapidly release a fix for this or even offer a preview image to unblock us.

---

<div class="post-metadata">

**Author:** ![ethiril](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ethiril/32/37015_2.png) [@ethiril](https://discuss.circleci.com/u/ethiril)\
**Post date:** [June 4, 2026, 3:23pm UTC](https://discuss.circleci.com/t/macos-26-4-update/54610/3 "2026-06-04T15:23:08Z")

</div>

My team is struggling with the same thing, is there any workaround we can use in the meanwhile?

---

<div class="post-metadata">

**Author:** ![Gigas002](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/gigas002/32/37008_2.png) [@Gigas002](https://discuss.circleci.com/u/Gigas002)\
**Post date:** [June 15, 2026, 7:16am UTC](https://discuss.circleci.com/t/macos-26-4-update/54610/4 "2026-06-15T07:16:04Z")

</div>

Any response from CircleCI team with schedule would be helpful, this problem really becomes worse and worse blocker for our team

---

<div class="post-metadata">

**Author:** ![cade](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/cade/32/37035_2.png) [@cade](https://discuss.circleci.com/u/cade)\
**Post date:** [June 18, 2026, 7:35pm UTC](https://discuss.circleci.com/t/macos-26-4-update/54610/5 "2026-06-18T19:35:25Z")

</div>

Hello,

Starting with Xcode 27.0 Beta 1 and Xcode 26.6.0 RC 2, Xcode images will be running macOS 26.5

---

<div class="post-metadata">

**Author:** ![Gigas002](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/gigas002/32/37008_2.png) [@Gigas002](https://discuss.circleci.com/u/Gigas002)\
**Post date:** [June 22, 2026, 1:04am UTC](https://discuss.circleci.com/t/macos-26-4-update/54610/6 "2026-06-22T01:04:42Z")

</div>

Great to hear that! Will this also apply to stable xcode images as well (26.6, 27.0)?

---

<div class="post-metadata">

**Author:** ![cade](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/cade/32/37035_2.png) [@cade](https://discuss.circleci.com/u/cade)\
**Post date:** [June 22, 2026, 6:40pm UTC](https://discuss.circleci.com/t/macos-26-4-update/54610/7 "2026-06-22T18:40:23Z")

</div>

Yes, all future Xcode image publications will be on at least macOS 26.5.1.

---

<div class="post-metadata">

**Author:** ![Milezdeep9](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/milezdeep9/32/36861_2.png) [@Milezdeep9](https://discuss.circleci.com/u/Milezdeep9)\
**Post date:** [June 22, 2026, 10:52pm UTC](https://discuss.circleci.com/t/macos-26-4-update/54610/8 "2026-06-22T22:52:19Z")

</div>

Dropping nuts on GMA fool
