Skip to content

Pin the macOS CI leg to macos-26 - #18

Merged
samartomar merged 1 commit into
mainfrom
ci-pin-macos-26
Oct 5, 2026
Merged

samartomar merged 1 commit into
mainfrom
ci-pin-macos-26

Conversation

@samartomar

Copy link
Copy Markdown
Owner

Summary

-        os: [windows-latest, macos-latest]
+        os: [windows-latest, macos-26]
 ...
-    runs-on: macos-latest
+    runs-on: macos-26

macos-latest is macos-26-arm64 today (macOS 26.6.2 Tahoe, Apple silicon), but it moves to the next macOS on GitHub's schedule without a change here. The Mac leg is meant to test the macOS the owner's new Mac runs, so it names 26. test_packaging checked the runner string and follows; one line in docs/mac-plan.md too.

Evidence

  • Before: runner log for suite (macos-latest, py3.12) on main@6ec6c2b: Image: macos-26-arm64, macOS 26.6.2 25G83.
    After: this PR's own suite (macos-26, py3.12) and swift helper compiles checks run on the pinned image.
  • uv run python -m unittest tests.test_packaging passes.

Merge Danger

Door: two-way

Blast Radius: CI

The suite runs on the same image it already used; only the label is fixed. When macOS 27 is wanted, it is a deliberate one-word change.

🤖 Generated with Claude Code

`macos-latest` resolves to the image macos-26-arm64 today (macOS 26.6.2,
Tahoe, Apple silicon: the PR #16 and #17 runs). It moves to the next
macOS on GitHub's schedule, with no change in this repository to show
it. The Mac leg exists to say Flow works on the Mac the owner is buying,
which runs 26, so the suite and the Swift helper build now name it.

test_packaging's platform check named the runner string, so it follows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@samartomar
samartomar merged commit 24c8987 into main Oct 5, 2026
4 checks passed
@samartomar
samartomar deleted the ci-pin-macos-26 branch October 5, 2026 13:56
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.

1 participant