Skip to content

merge queue: checking #19056 on release/v3.8.53 (570dbd0) - #19057

Closed
mergify[bot] wants to merge 3 commits into
release/v3.8.53from
mergify/merge-queue/8e428bfaaf
Closed

mergify[bot] wants to merge 3 commits into
release/v3.8.53from
mergify/merge-queue/8e428bfaaf

Conversation

@mergify

@mergify mergify Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch premium-camembert-srtepv of the release queue, to test #19056 before it merges into release/v3.8.53.

What this draft tests

Mergify checks that #19056 still passes CI on top of release/v3.8.53. CI runs on this draft's code, built in this order:

  1. release/v3.8.53 at 570dbd0
  2. #19056, the pull request of this batch

✨ Where it stands: closed

Merge queue reset: the base branch head moved outside the merge queue to a9df7d6.

Follow the release queue in the dashboard

What happens next

  • Mergify closes this draft.
  • #19056 is still in the queue.
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: 570dbd06ff3ba2c3bf104f2e7e30b91d939b3aa4
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 19056
    scopes: []
scopes: []
...
Required conditions of queue rule release for merge
Required conditions to stay in the queue

@mergify

mergify Bot commented Nov 4, 2026

Copy link
Copy Markdown
Author

Merge queue reset: the base branch head moved outside the merge queue to a9df7d6

@mergify mergify Bot closed this Nov 4, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/8e428bfaaf branch November 4, 2026 22:22
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