ci(mergify): upgrade configuration to current format

[mergify]

Caution

The transformed Mergify configuration is invalid or still contains deprecated fields that Mergify could not migrate automatically.
This can happen when the deprecated fields live under a shared key or behind YAML anchors — Mergify cannot know what these define, so it cannot modify them — or when a value has no automatic equivalent and needs a manual rewrite.
In order for the configuration to be valid, you will need to manually modify it.
Here is the list of the remaining deprecated fields:

• pull_request_rules → actions → merge → commit_message_template
• pull_request_rules → actions → merge → commit_message_template

---

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 → 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)
• 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)

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?

Almost! We got most of the way there, but a couple of manual steps are still needed before it's safe to merge — check what's flagged at the top of this description for what's left to do.

Do I need to do anything special after merging?

Yes — take care of the manual steps flagged at the top of this description first, then you're all set. It's also a good idea to give any custom configurations 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! 🎉

[github-actions]

🦙 MegaLinter status: ⚠️ WARNING

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
⚠️ COPYPASTE	jscpd	yes		12	no	2.28s
✅ EDITORCONFIG	editorconfig-checker	1		0	0	0.01s
✅ REPOSITORY	checkov	yes		no	no	20.59s
⚠️ REPOSITORY	devskim	yes		1	no	2.26s
✅ REPOSITORY	dustilock	yes		no	no	0.01s
✅ REPOSITORY	gitleaks	yes		no	no	0.8s
✅ REPOSITORY	git_diff	yes		no	no	0.01s
✅ REPOSITORY	grype	yes		no	no	43.88s
⚠️ REPOSITORY	kics	yes		6	no	1.35s
✅ REPOSITORY	secretlint	yes		no	no	1.49s
✅ REPOSITORY	syft	yes		no	no	2.81s
✅ REPOSITORY	trivy	yes		no	no	11.24s
✅ REPOSITORY	trivy-sbom	yes		no	no	0.17s
✅ REPOSITORY	trufflehog	yes		no	no	3.92s
⚠️ SPELL	cspell	2		9	0	3.96s
✅ SPELL	lychee	1		0	0	0.12s
⚠️ YAML	prettier	1		1	2	0.49s
✅ YAML	v8r	1		0	0	3.04s
✅ YAML	yamllint	1		0	0	0.51s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mergify]

Checks failed

Checks:

Name	Status
Configuration changed	✅
@mergify/Configuration changed	✅
CodeFactor	✅
@codefactor-io/CodeFactor	✅
label	✅
@github-actions/label	✅
Summary	✅
@mergify/Summary	✅
test	✅
@github-actions/test	✅
CommitCheck	✅
docs/readthedocs.org:i-language-rust	✅
pre-commit.ci - pr	✅
MegaLinter	❌
@github-actions/MegaLinter	❌

[mergify]

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

• Queue this pull request

[mergify]

Checks failed

Checks:

Name	Status
Configuration changed	✅
@mergify/Configuration changed	✅
CodeFactor	✅
@codefactor-io/CodeFactor	✅
label	✅
@github-actions/label	✅
Summary	✅
@mergify/Summary	✅
test	✅
@github-actions/test	✅
CommitCheck	✅
docs/readthedocs.org:i-language-rust	✅
pre-commit.ci - pr	✅
MegaLinter	❌
@github-actions/MegaLinter	❌

[mergify]

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

• Queue this pull request

[mergify]

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

• Queue this pull request

[mergify]

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

• Queue this pull request

[mergify]

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

• Queue this pull request

[mergify]

Checks failed

Checks:

Name	Status
Configuration changed	✅
@mergify/Configuration changed	✅
CodeFactor	✅
@codefactor-io/CodeFactor	✅
label	✅
@github-actions/label	✅
test	✅
@github-actions/test	✅
Summary	✅
@mergify/Summary	✅
CommitCheck	✅
pre-commit.ci - pr	✅
docs/readthedocs.org:i-language-rust	✅
MegaLinter	❌
@github-actions/MegaLinter	❌

[mergify]

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

• Queue this pull request

[mergify]

Checks failed

Checks:

Name	Status
Configuration changed	✅
@mergify/Configuration changed	✅
CodeFactor	✅
@codefactor-io/CodeFactor	✅
label	✅
@github-actions/label	✅
test	✅
@github-actions/test	✅
Summary	✅
@mergify/Summary	✅
docs/readthedocs.org:i-language-rust	✅
CommitCheck	✅
pre-commit.ci - pr	✅
MegaLinter	❌
@github-actions/MegaLinter	❌