fix: pull-v4-into-v4-next workflow never executes (switch push trigger to schedule)#21424
Closed
fix: pull-v4-into-v4-next workflow never executes (switch push trigger to schedule)#21424
Conversation
github-merge-queue bot
pushed a commit
that referenced
this pull request
Mar 12, 2026
…21425) ## Summary Replaces #21424 — same fix but with the workflow in `.github/` directly instead of `.github-new/`. The `pull-v4-into-v4-next` workflow has **208 runs and 0 successes** — it has never worked. PR merges (both manual and auto-merge) create push events using GitHub's internal `GITHUB_TOKEN`, and GitHub's anti-recursion protection prevents workflows triggered by those events from executing jobs. **Changes:** - Replace `on: push: branches: [v4]` with `on: schedule: cron '*/15 * * * *'` + `workflow_dispatch` - Add "Check if v4 is ahead of v4-next" step that skips the run when already synced - Gate all subsequent steps on `needs_merge == 'true'` - No other logic changes Supersedes #21424 ClaudeBox log: https://claudebox.work/s/4acfe00daf0aeff1?run=1
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
2 participants
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
The
pull-v4-into-v4-nextworkflow has 208 runs and 0 successes — it has never worked. This meansv4-nexthas been falling behindv4silently, requiring manual intervention to sync.Root cause: The workflow triggers on
pushtov4, but PR merges (both manual via the GitHub UI and auto-merge viagh pr merge --auto) create push events using GitHub's internalGITHUB_TOKEN. GitHub's anti-recursion protection prevents workflows triggered byGITHUB_TOKEN-created events from executing jobs — so the runs are created but immediately fail with 0 jobs.Fix: Replace the
pushtrigger with aschedulecron (every 15 minutes) +workflow_dispatch. Added an early-exit check (git rev-list --count v4-next..origin/v4) so runs are no-ops when branches are already in sync.Changes (proposed in
.github-new/)The modified workflow file is at
.github-new/workflows/pull-v4-into-v4-next.yml— copy it to.github/workflows/to apply.on: push: branches: [v4]withon: schedule: cron '*/15 * * * *'+workflow_dispatchneeds_merge == 'true'Context
PR #21355 was merged to
v4~16h ago but never forwarded tov4-next, blocking the nightly release from including those fixes.ClaudeBox log: https://claudebox.work/s/0d99ab68b1e8e26a?run=3