Skip to content

fix(cve): Address work around for cve-2026-22732#28

Open
jasonmcintosh wants to merge 2 commits into
release-1.36.xfrom
fixcve-2026-22732
Open

fix(cve): Address work around for cve-2026-22732#28
jasonmcintosh wants to merge 2 commits into
release-1.36.xfrom
fixcve-2026-22732

chore(formatting): Apply spotlessApply formatting

149e77d
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded May 8, 2026 in 5s

6 faulty rules

Rule: Automatically merge on CI success and review (queue)

  • approved-reviews-by=@oss-approvers ⚠️ Team @oss-approvers does not exist
  • base=master
  • label=ready to merge
  • status-success=build
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue rule default]

Rule: Automatically merge on CI success and review (label)

  • approved-reviews-by=@oss-approvers ⚠️ Team @oss-approvers does not exist
  • base=master
  • label=ready to merge
  • status-success=build

Rule: Automatically merge release branch changes on CI success and release manager review (queue)

  • approved-reviews-by=@release-managers ⚠️ Team @release-managers does not exist
  • label=ready to merge
  • status-success=build
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • base~=^release-
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue rule default]

Rule: Automatically merge release branch changes on CI success and release manager review (label)

  • approved-reviews-by=@release-managers ⚠️ Team @release-managers does not exist
  • label=ready to merge
  • status-success=build
  • base~=^release-

Rule: Automatically merge PRs from maintainers on CI success and review (queue)

  • author=@oss-approvers ⚠️ Team @oss-approvers does not exist
  • base=master
  • label=ready to merge
  • status-success=build
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue rule default]

Rule: Automatically merge PRs from maintainers on CI success and review (label)

  • author=@oss-approvers ⚠️ Team @oss-approvers does not exist
  • base=master
  • label=ready to merge
  • status-success=build
3 not applicable rules

Rule: Automatically merge autobump PRs on CI success (queue)

  • author:spinnakerbot
  • label~=autobump-*
  • status-success=build
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • base~=^(master|release-)
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue rule default]

Rule: Automatically merge autobump PRs on CI success (label)

  • author:spinnakerbot
  • label~=autobump-*
  • status-success=build
  • base~=^(master|release-)

Rule: Request reviews for autobump PRs on CI failure (request_reviews)

  • base=master
  • label~=autobump-*
  • base~=^(master|release-)
  • status-failure=build
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

View more details on Mergify