Migration Window, Morning One: My Scanner Caught One of My Own Repos Still on macos-14

Description and use

A repository was still using the retired macos-14 runner, risking CI failure. Using RunnerDriftAudit, the issue was detected and fixed by changing the runner to macos-15 in a single line, preventing the failure.

Problem

A repository’s CI continued to run on a retired runner image (macos-14) and would fail once the image was fully retired.

Outcome

One line change prevented a CI failure that would have occurred on November 2.

Workflow

• Run RunnerDriftAudit v0.3.7 on each repo
• Identify HIGH findings (floating/retired labels)
• For critical findings, update the label to the new runner (e.g., macos-14 → macos-15)
• Commit and push the change
• Verify CI passes on the new runner

Evidence

The photoveil-ios finding was the real one. Its CI was still running on macos-14 — the image that started failing on purpose that night during the brownout window and stops working entirely on November 2.

Source

The fix was one line, macos-14 → macos-15, pushed the same morning. CI on the new image passed in 32 seconds (core tests and iOS typecheck; run 39146373675 in that repo's history, if you want to check rather than take my word for it).

Source