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-01-31, otherwise your configuration will stop working.
What's Changed?
pull_request_rules → actions → queue → merge_method: To ease the configuration of queues, we are moving this attribute in the queue_rules definition. (deadline: 2025-01-31)
defaults → actions → queue → merge_method: To ease the configuration of queues, we are moving this attribute in the queue_rules definition. (deadline: 2025-01-31)
pull_request_rules → actions → queue → allow_merging_configuration_change: This option is no longer effective and can been safely removed from the configuration. (deadline: 2025-01-31)
defaults → actions → queue → allow_merging_configuration_change: This option is no longer effective and can been safely removed from the configuration. (deadline: 2025-01-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?
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.
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-01-31, otherwise your configuration will stop working.
What's Changed?
pull_request_rules → actions → queue → merge_method: To ease the configuration of queues, we are moving this attribute in thequeue_rulesdefinition. (deadline: 2025-01-31)defaults → actions → queue → merge_method: To ease the configuration of queues, we are moving this attribute in thequeue_rulesdefinition. (deadline: 2025-01-31)pull_request_rules → actions → queue → allow_merging_configuration_change: This option is no longer effective and can been safely removed from the configuration. (deadline: 2025-01-31)defaults → actions → queue → allow_merging_configuration_change: This option is no longer effective and can been safely removed from the configuration. (deadline: 2025-01-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?
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! 🎉