Skip to content

chore(release-pkg): release packages - #1724

Merged
mergify[bot] merged 1 commit into
devfrom
__release-pkg
Oct 28, 2026
Merged

mergify[bot] merged 1 commit into
devfrom
__release-pkg

chore(common): release packages

ebe9fda
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 28, 2026 in 1s

1 rule matches and 3 potential rules

✅ Rule: automatic approval for release package PR (review)

  • author~=^ConfluxBot$
  • base=dev
  • head=__release-pkg

Rule: automatic update PR with merge (update)

  • #commits-behind > 0 [📌 update requirement]
  • -closed [📌 update requirement]
  • -conflict
  • -conflict [📌 update requirement]
  • -draft
  • head!=dev
  • head!=main
  • label!=no-auto-merge-updates
  • label!=wip
  • label!=work-in-progress
  • queue-position = -1 [📌 update requirement]

Rule: Automatic queue to dev on approval (__release-pkg) (queue)

  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • author~=^ConfluxBot$
  • head=__release-pkg
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = @mergify/Configuration changed
    • check-success = @mergify/Configuration has been deleted
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue rule Automatic queue to dev on approval (__release-pkg)]
      • #approved-reviews-by>=1
      • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
      • #review-threads-unresolved=0
      • -conflict
      • -draft
      • -locked
      • base=dev
      • github-review-approved [🛡 GitHub branch protection]
      • head=__release-pkg
      • label!=no-auto-squash-merge
      • label!=wip
      • label!=work-in-progress
      • status-success~=^build\s\(.*\)$
      • any of: [🛡 GitHub branch protection]
        • check-success = build (22)
        • check-neutral = build (22)
        • check-skipped = build (22)

Rule: Automatic queue to dev on approval [low] (queue)

  • -closed [📌 queue requirement]
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue rule Automatic queue to dev on approval]
      • status-success~=^build-doc\s\(.*\)$
      • status-success~=^integration-test\s\(.*\)$
      • status-success~=^lint\s\(.*\)$
      • status-success~=^unit-test\s\(.*\)$
      • status-success~=^version-check\s\(.*\)$
      • #approved-reviews-by>=1
      • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
      • #review-threads-unresolved=0
      • -conflict
      • -draft
      • -locked
      • base=dev
      • github-review-approved [🛡 GitHub branch protection]
      • head!=next
      • label!=no-auto-squash-merge
      • label!=wip
      • label!=work-in-progress
      • status-success~=^build\s\(.*\)$
      • any of: [🛡 GitHub branch protection]
        • check-success = build (22)
        • check-neutral = build (22)
        • check-skipped = build (22)
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = @mergify/Configuration changed
    • check-success = @mergify/Configuration has been deleted

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