ci(mergify): upgrade configuration to current format #569
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
mergify
bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
23e40ea to
b686e79
Compare
|
* BE-659 | Update import paths
mergify
bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
b686e79 to
d05dfdf
Compare
… (#583) Adds backwards compatibility support for /pools endpoint allowing independent deployment of SQS (cherry picked from commit 16e9207) Co-authored-by: Deividas Petraitis <[email protected]>
Pipeline: require backport to v28.x (cherry picked from commit 7389cc7) Co-authored-by: Deividas Petraitis <[email protected]>
Fixes a bug when searching pool by pair of tokens for /pools endpoint (cherry picked from commit 1427db0) Co-authored-by: Deividas Petraitis <[email protected]>
Fixes a bug when searching pool by pair of tokens for /pools endpoint (cherry picked from commit 9262f80) Co-authored-by: Deividas Petraitis <[email protected]>
Updates CHANGELOG.md for v27.1.0 (cherry picked from commit 60ba6b3) Co-authored-by: Deividas Petraitis <[email protected]>
Introduces a denoms filter for /pools endpoint allowing to filter pools by given list of denoms (cherry picked from commit 242467f) Co-authored-by: Deividas Petraitis <[email protected]>
Updates CHANGELOG.md for v27.2.0 (cherry picked from commit 56663e8) Co-authored-by: Deividas Petraitis <[email protected]>
Fixes claimbot panics due nil routerrepo.RouterRepository in txGasCalulator (cherry picked from commit 8cb0091) Co-authored-by: Deividas Petraitis <[email protected]>
Upgrades osmosis images to 28.0.0
mergify
bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
d05dfdf to
ee0937a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 → commit_message_template: To ease the configuration of queues, we are moving this attribute in thequeue_rulesdefinition. (deadline: 2025-01-31)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)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! 🎉