Repository navigation
ci(release): filter release line pushes by path and drop the merge queue handling - #4162
Merged
Merged
Conversation
datlechin
enabled auto-merge (squash)
November 9, 2026 12:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ci.ymlPlan: every push, tomainor arelease/**line, compares with the last green CI push run on its own branch. A release PR's merge changes onlyapple/CHANGELOG.mdandapple/changelog.d/, which no suite reads, so its push runs Lint only. The first push of a new line has no green run, so it runs everything, as today.detect-changed-paths.shdrops--ref, which made arelease/**push run every suite (ci(release): check the tag's own CI runs instead of walking and polling #3584).version.py check: a test job the tag's CI push run left out (its calling job skipped by the plan) passes when that job passed at an ancestor on the line and the job's own suite (macosorios) has not changed since. Otherwise the errors are today's, plus the reason. Per job and per suite, notshippedwith both jobs: a macOS-only pick leaves the iOS tests last passing at the cut, soshippedwould refuse every tag after it, and no test job reads the release scripts inshipped.merge_grouptrigger, no merge-group base, no "the queue already passed" shortcut, no merge-group arm in Lint's changelog step. A main push now runs the suites whose paths changed since main's last green CI push run..claude/rules/ci.md, rootAGENTS.md(gh pr merge <N> --auto --squasheverywhere),apple/RELEASING.md(Branches records the reversal of ci(release): check the tag's own CI runs instead of walking and polling #3584; Forward-port merges with--squash),linux/docs/testing.md, two cache comments.release/0.86keeps its own files and still runs every suite on every push. This applies from the next line cut.Test plan
test_version.py: a release commit takes each test job from its last pass; a left-out job is refused after a change to its suite, or with no pass at an ancestor on the line; a failed job beside a left-out one is not excused. The three new refusal and pass tests fail on main.test_detect_changed_paths.py:test_a_release_branch_runs_every_suiteandtest_main_and_pull_request_refs_keep_the_path_filterpinned--refand are replaced bytest_a_release_pull_request_runs_no_suite(a release PR's diff selects no suite,shippedincluded).release/0.86runs returns no error; the detector fromea1eb4c2to the v0.86.0 release commitc3eb2f247selects no Apple suite.shellcheck --severity=warning, zizmor offline: clean. Release tooling andscripts/citests pass locally.