Skip to content

chore: add v4-next branch automation#21338

Merged
ludamad merged 1 commit intonextfrom
chore/v4-next-automation
Mar 10, 2026
Merged

chore: add v4-next branch automation#21338
ludamad merged 1 commit intonextfrom
chore/v4-next-automation

Conversation

@ludamad
Copy link
Collaborator

@ludamad ludamad commented Mar 10, 2026

Summary

  • Adds pull-v4-into-v4-next.yml workflow: on every push to v4, automatically merges into v4-next. If conflicts arise, creates a PR for manual resolution.
  • Adds nightly-release-tag-v4-next.yml workflow: tags v4-next nightly at 05:00 UTC with v{version}-nightly.{date} format.

Copy link
Contributor

@nventuro nventuro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

love you adam tyvm

## Summary

- Adds `pull-v4-into-v4-next.yml` workflow: on every push to `v4`, automatically merges into `v4-next`. If conflicts arise, creates a PR for manual resolution.
- Adds `nightly-release-tag-v4-next.yml` workflow: tags `v4-next` nightly at 02:00 UTC with `v{version}-nightly.{date}` format.
@AztecBot AztecBot force-pushed the chore/v4-next-automation branch from 4415a47 to b6965d5 Compare March 10, 2026 22:24
@ludamad ludamad added this pull request to the merge queue Mar 10, 2026
Merged via the queue into next with commit 7ea253c Mar 10, 2026
21 checks passed
@ludamad ludamad deleted the chore/v4-next-automation branch March 10, 2026 22:58
ludamad added a commit that referenced this pull request Mar 11, 2026
## Summary

Backport of the sync workflow to `v4` so the `push` trigger fires when
commits land on `v4`.

- `pull-v4-into-v4-next.yml`: on every push to `v4`, merges into
`v4-next`. Creates a conflict-resolution PR if needed.

The nightly tag job and backport infrastructure are handled from the
default branch (`next`) via PR #21338.
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.

3 participants