Bump cachetools from 6.2.2 to 6.2.4 in /flowmachine #7213
+3
−3
Mergify / Summary
succeeded
Jan 28, 2026 in 1s
2 potential rules
Rule: Automatic merge for approved PRs labelled as ready (merge)
-
#approved-reviews-by>=1 -
#commits-behind = 0[🛡 GitHub branch protection] -
label=ready-to-merge -
status-success=run_build_pipeline - any of: [🛡 GitHub branch protection]
-
check-neutral = run_build_pipeline -
check-skipped = run_build_pipeline -
check-success = run_build_pipeline
-
-
-closed[📌 merge requirement] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] -
base=master - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
Rule: Automatic merge for Dependabot pull requests (merge)
-
#commits-behind = 0[🛡 GitHub branch protection] -
status-success=run_build_pipeline - any of: [🛡 GitHub branch protection]
-
check-neutral = run_build_pipeline -
check-skipped = run_build_pipeline -
check-success = run_build_pipeline
-
-
-closed[📌 merge requirement] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] -
author=dependabot[bot] -
base=master - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
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