Repository navigation
ci: pause merge-main while Wave 3 release candidates are on next - #598
Merged
Merged
Conversation
Mukesh-FN
requested review from
AlanFnz,
Amin52J,
chrisrolfe198 and
lizzielerwill-ctrl
as code owners
October 14, 2026 11:22
commit: |
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
1 participant
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.
What
Stops copying every change on
mainintonextautomatically, while Wave 3 is being tested onnext(#576).Why
While Wave 3 is tested,
mainkeeps getting Wave 2 changes. Wave 3 is built differently, so a Wave 2 change copied over as it is may not work there, and nothing would catch it. Copying would also start failing after the next Wave 2 release.How
Merging
Merge before #576.