Skip to content

fix: merge-train/fairies should merge from v4 not next#20728

Draft
ludamad wants to merge 2 commits intonextfrom
ad/fix/merge-train-fairies-v4-target
Draft

fix: merge-train/fairies should merge from v4 not next#20728
ludamad wants to merge 2 commits intonextfrom
ad/fix/merge-train-fairies-v4-target

Conversation

@ludamad
Copy link
Collaborator

@ludamad ludamad commented Feb 20, 2026

Configures merge-train/fairies to target and merge from the v4 branch instead of next. This ensures the correct base branch is used for this specific merge train and prevents incorrect merges to the next branch. The change aligns merge behavior with v4 release requirements.

- Remove merge-train/fairies from the next-to-branches sync matrix
- Add merge-train-v4-to-branches.yml to sync v4 into merge-train/fairies
- Update merge-train-create-pr.yml to target v4 for merge-train/fairies,
  including ancestor check and PR body README link
- Generalize merge-next.sh to accept an optional source branch argument
  (defaults to next) so it can merge from v4
- Update SKILL.md docs to reflect the fairies v4 exception
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant