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

What's Changed?

• queue_rules → commit_message_template: The commit_message_template setting is deprecated. Use the declarative commit_message_format instead: https://docs.mergify.com/workflow/actions/merge#migrating-from-commit_message_template (deadline: 2026-09-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! 🎉

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-02 22:43 UTC · Rule: default · triggered by merge protections
• 🟠 Checks running · on draft merge queue: checking main (390edd2) and #566 together #567
• 🚫 Left the queue — 2026-07-02 22:49 UTC · at c5bc79b784fb6f7184da2fb7a3980044c577d88a

This pull request spent 5 minutes 45 seconds in the queue, including 3 seconds running CI.

Waiting for

• #approved-reviews-by>=1
• check-success=PR Status Check
• any of: [🛡 GitHub branch protection]
  • check-neutral = PR Status Check
  • check-skipped = PR Status Check
  • check-success = PR Status Check
• any of: [🛡 GitHub repository ruleset rule main]
  • check-neutral = @github-actions/PR Status Check
  • check-skipped = @github-actions/PR Status Check
  • check-success = @github-actions/PR Status Check

All conditions

• #approved-reviews-by>=1
  • ci(mergify): upgrade configuration to current format #566
• check-success=PR Status Check
• any of [🛡 GitHub branch protection]:
  • check-neutral = PR Status Check
  • check-skipped = PR Status Check
  • check-success = PR Status Check
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = @github-actions/PR Status Check
  • check-skipped = @github-actions/PR Status Check
  • check-success = @github-actions/PR Status Check
• #changes-requested-reviews-by=0
  • ci(mergify): upgrade configuration to current format #566
• #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule main]
  • ci(mergify): upgrade configuration to current format #566

Reason

Pull request #566 has been dequeued

merge conditions no longer match. Blocked by:

• #approved-reviews-by>=1

• #approved-reviews-by>=1

• check-success=PR Status Check

• any of [🛡 GitHub branch protection]:

  • check-neutral = PR Status Check
  • check-skipped = PR Status Check
  • check-success = PR Status Check

• any of [🛡 GitHub repository ruleset rule main]:

  • check-neutral = @github-actions/PR Status Check
  • check-skipped = @github-actions/PR Status Check
  • check-success = @github-actions/PR Status Check

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, 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 queue comment.

Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).

• Requeue this pull request