ci(mergify): upgrade configuration to current format

[mergify]

Caution

Your Mergify configuration uses deprecated fields that Mergify cannot migrate automatically.
This pull request does not modify your configuration — it exists to make sure you see this notice.

Hey there! 👋

We've noticed that your Mergify configuration is using some deprecated fields. Mergify usually updates them for you automatically, but these ones have no exact automatic replacement — migrating them could change how your rules behave, so they need your judgment:

• pull_request_rules → actions → merge → 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)

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

What should I do?

Update the fields listed above directly in your configuration file, following the documentation linked in each item. Once your default branch no longer uses them, this pull request will close automatically — there is nothing to merge here.

Got Questions? We've Got Answers! 🙌

Why didn't Mergify migrate this for me?

The new syntax cannot reproduce your current configuration exactly. Rather than risk changing your workflows' behavior, we leave the migration to you.

What if I run into issues or have concerns?

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

Happy merging! 🎉

[codeant-ai]

Skipping PR review because a bot author is detected.

If you want to trigger CodeAnt AI, comment @codeant-ai review to trigger a manual review.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[github-actions]

L17 Latency Budget Report

--- Latency Budget Summary ---
  Total endpoints checked: 0
  Passed: 0
  Warnings: 0
  Failures: 0

Checked against: budgets/rest-endpoints.yaml.

[github-actions]

L17 Latency Regression Report

No trace file available — cannot compute regression

Threshold: 10% p99 regression.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud