chore: Bump @aws-sdk/client-ecs from 3.653.0 to 3.658.0 #330
Mergify / Summary
succeeded
Sep 26, 2024 in 12s
2 potential rules
The configuration uses the deprecated
merge_method
attribute of the queue action in one or morepull_request_rules
. It must now be used under thequeue_rules
configuration.
A brownout is planned on September 16th, 2024.
This option will be removed on October 21st, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
Rule: Automatically approve and merge Dependabot PRs (queue)
-
-closed
-
-closed
[📌 queue requirement] -
-merged
-
-conflict
[📌 queue requirement] -
-draft
[📌 queue requirement] -
-label~=(blocked|do-not-merge)
-
-title~=(WIP|wip)
-
author=dependabot[bot]
-
base=master
-
status-success=Run Unit Tests
-
status-success=Semantic Pull Request
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
#approved-reviews-by >= 1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success = Analyze (javascript)
-
check-neutral = Analyze (javascript)
-
check-skipped = Analyze (javascript)
-
- any of: [🛡 GitHub branch protection]
-
check-success = Package distribution file
-
check-neutral = Package distribution file
-
check-skipped = Package distribution file
-
- any of: [🛡 GitHub branch protection]
-
check-success = Semantic Pull Request
-
check-neutral = Semantic Pull Request
-
check-skipped = Semantic Pull Request
-
-
- all of: [📌 queue conditions of queue
Rule: Automatically approve and merge Dependabot PRs (review)
-
-closed
-
-merged
-
-label~=(blocked|do-not-merge)
-
-title~=(WIP|wip)
-
author=dependabot[bot]
-
base=master
-
status-success=Run Unit Tests
-
status-success=Semantic Pull Request
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
1 not applicable rule
Rule: Automatically merge on CI success and review approval (queue)
-
-closed
-
-closed
[📌 queue requirement] -
-merged
-
approved-reviews-by=@aws-actions/aws-ecs-devx
-
author!=dependabot[bot]
-
#approved-reviews-by>=1
-
-approved-reviews-by~=author
-
-conflict
[📌 queue requirement] -
-draft
[📌 queue requirement] -
-title~=(WIP|wip)
-
base~=master|integ-tests
-
label!=work-in-progress
-
status-success=Run Unit Tests
-
status-success=Semantic Pull Request
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
#approved-reviews-by >= 1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success = Analyze (javascript)
-
check-neutral = Analyze (javascript)
-
check-skipped = Analyze (javascript)
-
- any of: [🛡 GitHub branch protection]
-
check-success = Package distribution file
-
check-neutral = Package distribution file
-
check-skipped = Package distribution file
-
- any of: [🛡 GitHub branch protection]
-
check-success = Semantic Pull Request
-
check-neutral = Semantic Pull Request
-
check-skipped = Semantic Pull Request
-
-
- all of: [📌 queue conditions of queue
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
Loading