ci(mergify): upgrade configuration to current format

[mergify]

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 2025-06-30, otherwise your configuration will stop working.

What's Changed?

• The implicit priority for the queue rules, that was based on their order, is going to be removed in favor of using priority_rules.
  This transformation aim to create priority rules, based on your existing queue rules, in order to keep the same priorities. If this priority change is not needed for you, you should not close this pull request until the deadline, otherwise it will be re-created again. (deadline: 2025-06-30)

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! 🎉

[ulysses4ever]

Superficially, this looks fine to me.

[geekosaur]

This actually has a problem: it somehow missed that we have two queues (default and squash-merge) and doesn't set the priority for the latter. I will fix.

[Mikolaj]

This won't be backported, right? 3.14 is not LTS for sure.

[ulysses4ever]

Oh, good catch, @geekosaur , thanks!

[ulysses4ever]

but if we'll want another point release, we might need it. For the current one, we might skip it for expediency?..

[geekosaur]

It's Mergify config, it does nothing whatsoever on branches. Mergify only pays attention to master.

[ulysses4ever]

allrighty!

[Mikolaj]

LGTM

[Mikolaj]

@geekosaur: you are the CI guru, would you set the merge label?

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.