Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: bump version to v22 #3413

Merged
merged 5 commits into from
Nov 28, 2024

fix: v21 -> v22 in interchaintest

61a0927
Select commit
Loading
Failed to load commit list.
Merged

chore: bump version to v22 #3413

fix: v21 -> v22 in interchaintest
61a0927
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 28, 2024 in 1s

4 potential rules

⚠️ The pull request has been merged by @mpoke

Rule: Automatic merge on approval to the main branch (merge)

  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
  • label=A:automerge
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • base=main
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = golangci-lint
    • check-neutral = golangci-lint
    • check-skipped = golangci-lint
  • any of: [🛡 GitHub branch protection]
    • check-success = test-e2e
    • check-neutral = test-e2e
    • check-skipped = test-e2e
  • any of: [🛡 GitHub branch protection]
    • check-success = tests
    • check-neutral = tests
    • check-skipped = tests

Rule: Automatic merge on approval to the main branch (queue)

  • -closed [📌 queue requirement]
  • label=A:automerge
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
      • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success = golangci-lint
        • check-neutral = golangci-lint
        • check-skipped = golangci-lint
      • any of: [🛡 GitHub branch protection]
        • check-success = test-e2e
        • check-neutral = test-e2e
        • check-skipped = test-e2e
      • any of: [🛡 GitHub branch protection]
        • check-success = tests
        • check-neutral = tests
        • check-skipped = tests
  • #approved-reviews-by>=1
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • base=main
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Backport patches to the release/v21.x branch (backport)

  • label=A:backport/v21.x
  • base=main
  • merged [📌 backport requirement]

Rule: Backport patches to the release/v20.x branch (backport)

  • label=A:backport/v20.x
  • base=main
  • merged [📌 backport requirement]

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com