ci(mergify): upgrade configuration to current format #631
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}
… migrate` (backport cosmos#22057) (cosmos#22070) Co-authored-by: tutufen <[email protected]>
…mos#22090) (cosmos#22097) Co-authored-by: tutufen <[email protected]>
Co-authored-by: Julien Robert <[email protected]>
…21782) (cosmos#22228) Co-authored-by: Luis Carvalho <[email protected]> Co-authored-by: Julien Robert <[email protected]>
…s#22231) Co-authored-by: Julien Robert <[email protected]>
… (cosmos#22432) Co-authored-by: Julien Robert <[email protected]>
…#22443) (cosmos#22445) Co-authored-by: Julien Robert <[email protected]>
…22463) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: sontrinh16 <[email protected]>
…s#22573) Co-authored-by: Julien Robert <[email protected]>
…(backport cosmos#22576) (cosmos#22615) Co-authored-by: violet <[email protected]> Co-authored-by: Julien Robert <[email protected]>
mergify
bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
22dbff3 to
8c57564
Compare
…smos#22638) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Julien Robert <[email protected]>
…22662) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Julien Robert <[email protected]>
…mos#22821) Co-authored-by: Julián Toledano <[email protected]> Co-authored-by: Julien Robert <[email protected]>
…89a02871 to 0.13.6 (cosmos#22844) Co-authored-by: Julien Robert <[email protected]>
…2884) Co-authored-by: Julien Robert <[email protected]>
* Limit recursion depth for unknown field detection (cherry picked from commit f038dc731c55be1e1c526e67695acc358631afd6) * Limit unpack any (cherry picked from commit 1a2bff56fb7391f9ce87d4fbe9e0367ae991c0b2) * Update Changelog * Another limit recursion depth for unknown field detection * Update changelog
|
This pull request 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. |
* chore: bump IAVL to latest version for speed up * chore: add CHANGELOG.md
mergify
bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
8c57564 to
5110fe7
Compare
github-actions
bot
added
C:x/genutil
C:Keys
C:CLI
C:Store
C:x/group
C:x/tx
and removed
Stale
labels
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! 🎉