Repository navigation
ci: move macOS legs to the macos-15 runner label - #171
Conversation
Use the current hosted macOS runner label in both pull-request and post-merge native-feed workflows. Keep all other workflow behavior unchanged.
Move the native feed policy expectations and matrix mutation fixtures to the current macOS runner label while keeping the retired macos-14 route as a negative control.
There was a problem hiding this comment.
Graphify reviewed this change.
No issues found by static checks — no coupling regressions or blocking issues in the code graph. That is not the same as safe to merge: see what was not checked.
Not checked: tests were not run; no formal proof of the changed code.
Graphify review — findings
Moves the native-feed macOS release legs from the macos-14 runner to macos-15, in both the PR-tier matrix and the post-merge release-macos job. The job name and PF_CI_LABELS value change with the runner. The workflow tests now pin macos-15 as the only hosted macOS runner, and the negative-matrix cases are updated to match. They still reject fallbacks, wrong pools, and missing or extra legs, and a few stale "old:" comments are rewritten.
No blocking issues surfaced.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 122 functions depend on the 122 functions this change touches.
Health — grade A; 2 existing hotspot(s) in the area this change touches (pre-existing, not introduced here):
classify()— 6 callers, 3 callees (medium)assert_cheap_pr_policy()— 5 callers, 3 callees (medium)
Verification — 122 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 122 function(s) in the blast radius were not formally verified this run
Summary
The macOS legs of
native-feed.yml(pull requests) andnative-feed-post.yml(main) asked for themacos-14runner label. Recent jobs on that label were cancelled about one second after start, before any runner was assigned (runner id 0, no steps), on both pull-request and main runs. This moves both workflows tomacos-15. The workflow policy tests that pin the label are updated to match.Tests
tests/test_post_merge_workflows.pyandtests/test_pr_tier_workflows.pypass on this head, and also on its parent as a control.🤖 Generated with Claude Code