Skip to content

merge queue: embarking main (2260a11) and #10931 together#11008

Closed
mergify[bot] wants to merge 2 commits intomainfrom
mergify/merge-queue/ca6d55c6b7
Closed

merge queue: embarking main (2260a11) and #10931 together#11008
mergify[bot] wants to merge 2 commits intomainfrom
mergify/merge-queue/ca6d55c6b7

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Apr 13, 2026

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (2260a11) and #10931 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #10931.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 2260a112316f37e56f92f19cccd7db9772350604
previous_failed_batches: []
pull_requests:
  - number: 10931
    scopes: []
scopes: []
...

kozlek and others added 2 commits April 8, 2026 17:52
The Vitest integration now uses the native `@mergifyio/vitest` reporter
plugin instead of JUnit XML generation + upload. This aligns with the
approach used by pytest-mergify and rspec-mergify.

Fixes MRGFY-6881

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Change-Id: I84d3bc46744df1353f94b8843d85fc2e8c22d411
Claude-Session-Id: 0a6db61c-3fec-4343-9ae3-dfbc7b2e9e31
@mergify mergify bot deployed to Mergify Merge Protections April 13, 2026 11:23 Active
@mergify mergify bot closed this Apr 13, 2026
@mergify mergify bot deleted the mergify/merge-queue/ca6d55c6b7 branch April 13, 2026 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant