Skip to content

Automatic merge from release/2.10 -> release/2.11#429

Merged
ben-gineer merged 13 commits intorelease/2.11from
release/2.10
Mar 20, 2026
Merged

Automatic merge from release/2.10 -> release/2.11#429
ben-gineer merged 13 commits intorelease/2.11from
release/2.10

Conversation

@github-actions
Copy link
Copy Markdown

This PR was created automatically by the cascading downstream merge action.

@ben-gineer ben-gineer merged commit 337835a into release/2.11 Mar 20, 2026
6 checks passed
@github-actions
Copy link
Copy Markdown
Author

Skipping creation of cascading PR to merge release/2.10 into release/2.11

There are no commits between these branches.

Continuing auto-merge action...

@github-actions
Copy link
Copy Markdown
Author

❗ Tried to create a cascading PR to merge release/2.11 into release/2.12 but there is already a pull request open.

Can't continue auto-merge action.

1 similar comment
@github-actions
Copy link
Copy Markdown
Author

❗ Tried to create a cascading PR to merge release/2.11 into release/2.12 but there is already a pull request open.

Can't continue auto-merge action.

@github-actions
Copy link
Copy Markdown
Author

‼️ Auto-merge action did not complete successfully. Please review issues.

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