‼️ Action Required ‼️

**The configuration uses the deprecated speculative_checks attribute in the queue_rules section. It has been replaced in favor of max_parallel_checks in the merge_queue section of the configuration.
For more information: https://docs.mergify.com/merge-queue/speculative-checks/

Rule: automatic merge to main (queue)

• #approved-reviews-by >= 1
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• label = "merge"
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue main-queue]
    • #approved-reviews-by >= 1
    • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-neutral = test-e2e (0)
      • check-skipped = test-e2e (0)
      • check-success = test-e2e (0)
    • any of: [🛡 GitHub branch protection]
      • check-neutral = test-e2e (1)
      • check-skipped = test-e2e (1)
      • check-success = test-e2e (1)
    • any of: [🛡 GitHub branch protection]
      • check-neutral = test-e2e (2)
      • check-skipped = test-e2e (2)
      • check-success = test-e2e (2)
    • any of: [🛡 GitHub branch protection]
      • check-neutral = test-e2e (3)
      • check-skipped = test-e2e (3)
      • check-success = test-e2e (3)
    • any of: [🛡 GitHub branch protection]
      • check-neutral = test-e2e (4)
      • check-skipped = test-e2e (4)
      • check-success = test-e2e (4)
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
    • base = main
    • any of: [🛡 GitHub branch protection]
      • check-success = test-e2e-with-device-automation
      • check-neutral = test-e2e-with-device-automation
      • check-skipped = test-e2e-with-device-automation
    • any of: [🛡 GitHub branch protection]
      • check-success = check-benchmarks
      • check-neutral = check-benchmarks
      • check-skipped = check-benchmarks
    • any of: [🛡 GitHub branch protection]
      • check-success = check-packages
      • check-neutral = check-packages
      • check-skipped = check-packages
    • any of: [🛡 GitHub branch protection]
      • check-success = build-binaries
      • check-neutral = build-binaries
      • check-skipped = build-binaries
    • any of: [🛡 GitHub branch protection]
      • check-success = build-wasm (wasm-for-tests, build-wasm-tests-scripts, wasm_for_tests/*.wasm)
      • check-neutral = build-wasm (wasm-for-tests, build-wasm-tests-scripts, wasm_for_tests/*.wasm)
      • check-skipped = build-wasm (wasm-for-tests, build-wasm-tests-scripts, wasm_for_tests/*.wasm)
    • any of: [🛡 GitHub branch protection]
      • check-success = lints
      • check-neutral = lints
      • check-skipped = lints
    • any of: [🛡 GitHub branch protection]
      • check-success = rust-docs
      • check-neutral = rust-docs
      • check-skipped = rust-docs
    • any of: [🛡 GitHub branch protection]
      • check-success = test-wasm
      • check-neutral = test-wasm
      • check-skipped = test-wasm
    • any of: [🛡 GitHub branch protection]
      • check-success = test-integration
      • check-neutral = test-integration
      • check-skipped = test-integration
    • any of: [🛡 GitHub branch protection]
      • check-success = test-unit
      • check-neutral = test-unit
      • check-skipped = test-unit
    • any of: [🛡 GitHub branch protection]
      • check-neutral = Mergify Merge Protections
      • check-skipped = Mergify Merge Protections
      • check-success = Mergify Merge Protections
• -closed [📌 queue requirement]
• base = main
• label != "do-not-merge"
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

Rule: notify when a PR is removed from the queue (comment)

• queue-dequeue-reason != none
• queue-dequeue-reason != pr-merged

Rule: backport PR to 0.44.0 lane (backport)

• label = backport-44
• 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