fix: run compatibility tests on all v4-related branches#22149
Merged
Conversation
The regex for triggering testnet_compatibility and mainnet_compatibility tests only matched branches like 'v4' (^v[0-9]+$). This missed PRs targeting backport-to-v4-staging, v4-next, and backport-to-v4-next. Expanded the regex to match all four branch patterns.
AztecBot
added
ci-draft
alexghr
approved these changes
Mar 30, 2026
AztecBot
pushed a commit
that referenced
this pull request
Mar 30, 2026
## Summary The `testnet_compatibility` and `mainnet_compatibility` tests were only running on PRs targeting branches matching `^v[0-9]+$` (e.g. `v4`). This missed three other critical branches: - `backport-to-v4-staging` - `v4-next` - `backport-to-v4-next` This caused a compatibility break on staging-public (4.2.0-aztecnr.2 bricking nodes due to block header shape changes between 4.1 and 4.2) to go undetected. ## Fix Expanded the regex in `yarn-project/bootstrap.sh` to: ``` ^(v[0-9]+(-next)?|backport-to-v[0-9]+-(staging|next))$ ``` This matches all four required branch patterns while still excluding `next`, `master`, and other non-release branches. ClaudeBox log: https://claudebox.work/s/dd9d82043dbc175f?run=1
Collaborator
Author
|
✅ Successfully backported to backport-to-v4-staging #22155. |
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
testnet_compatibilityandmainnet_compatibilitytests were only running on PRs targeting branches matching^v[0-9]+$(e.g.v4). This missed three other critical branches:backport-to-v4-stagingv4-nextbackport-to-v4-nextThis caused a compatibility break on staging-public (4.2.0-aztecnr.2 bricking nodes due to block header shape changes between 4.1 and 4.2) to go undetected.
Fix
Expanded the regex in
yarn-project/bootstrap.shto:This matches all four required branch patterns while still excluding
next,master, and other non-release branches.ClaudeBox log: https://claudebox.work/s/dd9d82043dbc175f?run=1