add release 4.1 to mergify

[heni02]

What type of PR is this?

• API-change
• BUG
• Improvement
• Documentation
• Feature
• Test and CI
• Code Refactoring

Which issue(s) this PR fixes:

issue #25337

What this PR does / why we need it:

add release 4.1 to mergify

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[mergify]

Caution

The updated Mergify configuration is adding new deprecated fields:

• queue_rules → commit_message_template
• queue_rules → commit_message_template
• queue_rules → commit_message_template
• queue_rules → commit_message_template
• queue_rules → commit_message_template
• queue_rules → commit_message_template

[mergify]

Merge Protections

🟢 Merge protection satisfied — ready to merge.

Show 1 satisfied protection

🟢 📃 Configuration Change Requirements

Mergify configuration change

• check-success = Configuration changed

[XuPeng-SH]

LGTM.

This is a clean config-only change: it adds the missing release-4.1 queue entry and the matching auto-queue rule for base = 4.1-dev, following the existing release-4.0 pattern.

I don’t see a substantive issue here. The only practical caveat is operational rather than code-related: just make sure 4.1-dev is indeed the intended branch name / rollout target when this lands.