ci(mergify): upgrade configuration to current format

[mergify]

Caution

The transformed Mergify configuration is invalid or contains deprecated fields that should have been transformed.
The shared key in your configuration could be the cause, Mergify cannot know what is inside this shared key so it cannot modify it.
In order for the configuration to be valid, you will need to manually modify it.
Here is the list of the remaining deprecated fields:

• defaults → actions → queue → update_method
• defaults → actions → queue → method
• pull_request_rules → actions → queue → method
• pull_request_rules → actions → queue → update_method
• pull_request_rules → actions → queue → method
• pull_request_rules → actions → queue → update_method

---

Hey there! 👋

We've noticed that your Mergify configuration is using some deprecated fields.

No worries—we've got your back! This automated PR updates your config to align with the newest standards, ensuring everything keeps running smoothly.

Do not procrastinate! You must upgrade your configuration before 2026-07-31, otherwise your configuration will stop working.

What's Changed?

• pull_request_rules → actions → delete_head_branch: The delete_head_branch action is deprecated. Use GitHub's native 'Automatically delete head branches' setting instead: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches (deadline: 2026-07-31)
• queue_rules → conditions: conditions in queue rule configuration is deprecated. Use merge_conditions instead. (deadline: 2026-07-31)

Why This Matters

Keeping your configuration up-to-date means you'll benefit from the latest features and improvements Mergify has to offer. Plus, it helps prevent any unexpected hiccups down the road.

Got Questions? We've Got Answers! 🙌

Is this update safe to merge?

Absolutely! We've made sure the changes are compatible with your current setup. Your workflows should continue to work just as before—if not better!

Do I need to do anything special after merging?

Nope! Just merge this PR, and you're all set. If you have any custom configurations, it's a good idea to give them a quick look to ensure everything's in order.

What if I run into issues or have concerns?

We're here to help! Feel free to reach out to our support team anytime.

Thanks for being awesome and keeping your configuration up-to-date! If you have any thoughts or need a hand, don't hesitate to let us know.

Happy merging! 🎉

[nixpanic]

this queue_conditions does not look right. It has both

• label!=design
• label=design

base is 2x in the list as well as others.

[nixpanic]

This rule really confuses me. It might be correct to try-and-queue everything, and remove things from the queue if queue_conditions are not met. But I think it could be written in an easier to understand way (or with extra comments).

[nixpanic]

I still don't understand this rule