chore(deps): bump actions/attest-build-provenance from 3.0.0 to 4.2.2 - #519
Merged
KooshaPari merged 1 commit intoAug 22, 2026
Mergify / Summary
succeeded
Aug 23, 2026 in 2s
1 rule matches and 7 potential rules
commit_message_template is deprecated and will be removed on 2026-09-30. Use the declarative commit_message_format instead: https://docs.mergify.com/workflow/actions/merge#migrating-from-commit_message_template
Rule: Auto-merge when approved + CI green (merge)
-
#approved-reviews-by>=1 -
#commits-behind = 0[🛡 GitHub branch protection] -
#review-requested=0 -
check-success=ci -
check-success=lint -
check-success=test -
check-success=typecheck -
github-review-approved[🛡 GitHub branch protection] -
#review-threads-unresolved = 0[🛡 GitHub branch protection] -
-closed -
-closed[📌 merge requirement] -
-conflict -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [📌 merge requirement]
-
check-neutral = Mergify Merge Protections -
check-skipped = Mergify Merge Protections -
check-success = Mergify Merge Protections
-
- any of: [🛡 GitHub branch protection]
-
check-success = ci / lint -
check-neutral = ci / lint -
check-skipped = ci / lint
-
- any of: [🛡 GitHub branch protection]
-
check-success = ci / test -
check-neutral = ci / test -
check-skipped = ci / test
-
✅ Rule: Request review from team (request_reviews)
-
-closed -
-draft
Rule: Label Python changes (label)
-
files~=\.py$
Rule: Label Rust changes (label)
-
files~=\.rs$|Cargo\.
Rule: Label Go changes (label)
-
files~=\.go$|go\.
Rule: Label TypeScript changes (label)
-
files~=\.ts$|\.tsx$|package\.json
Rule: Warn on large PRs (comment)
-
#files>20 -
-closed -
-draft
Rule: Add ready-to-merge label (label)
-
#approved-reviews-by>=1 -
check-success=ci -
check-success=lint -
check-success=test -
-closed -
-draft
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 refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill 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
Loading