chore: backport merge-train/spartan-v5 wiring to v5-next#23860
Merged
Conversation
Backports the merge-train/spartan-v5 wiring from #23831 (merged to next) onto v5-next. Until v5-next physically contains the updated merge-train-next-to-branches.yml, pushes to v5-next don't trigger the base->train sync (push events run the workflow from the pushed branch's own copy), so commits landing on v5-next never reach merge-train/spartan-v5. This puts the wiring on v5-next so that sync fires going forward.
AztecBot
added
ci-draft
spalladino
approved these changes
Jun 4, 2026
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.
Backports the
merge-train/spartan-v5wiring from #23831 (merged tonext) ontov5-next.Why this is needed
The base→train sync (
merge-train-next-to-branches.yml) is push-triggered, and for apushevent GitHub Actions runs the workflow file as it exists on the pushed branch.v5-nextstill has the old workflow (triggers only onnext, nospartan-v5routing), so commits landing onv5-nextnever fire the sync intomerge-train/spartan-v5. Putting the wiring onv5-nextmakes that sync fire for every subsequent push tov5-next.This is a cherry-pick of #23831's squashed commit onto
v5-next— same 12-file changeset, no v5-specific divergence (the merge-train infra files merged cleanly; v5-next's neweractions/checkoutpin is preserved).After merge
Future pushes to
v5-nextwill sync intomerge-train/spartan-v5. The commit that already landed onv5-next(chore: backport merge-train/spartan PRs to v5-next#23846) won't retroactively trigger — it needs either a fresh push tov5-nextor a one-time manualscripts/merge-train/merge-next.sh merge-train/spartan-v5 v5-nextto catch the train up.Labeled
ci-skip— workflow/script/docs config only.Created by claudebox · group:
slackbot