Skip to content

chore(merge-back): 2.220.0 #35740

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 5 commits into from
Oct 14, 2025
Merged

chore(merge-back): 2.220.0 #35740

merged 5 commits into from
Oct 14, 2025

Conversation

aws-cdk-automation
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation commented Oct 14, 2025 •
edited
Loading

See CHANGELOG

@aws-cdk-automation aws-cdk-automation requested a review from a team as a code owner October 14, 2025 14:07
@aws-cdk-automation aws-cdk-automation added auto-approve pr/no-squash This PR should be merged instead of squash-merging it labels Oct 14, 2025
@aws-cdk-automation aws-cdk-automation requested a review from a team October 14, 2025 14:07
@github-actions github-actions bot added the p2 label Oct 14, 2025
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Oct 14, 2025
@aws-cdk-automation aws-cdk-automation added the pr/needs-maintainer-review This PR needs a review from a Core Team Member label Oct 14, 2025
@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025

Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify mergify bot added the queued label Oct 14, 2025
@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #35740 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: Required status check "validate-pr" is queued.).

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify mergify bot removed the queued label Oct 14, 2025
@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025

Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork).

@kumvprat
Copy link
Contributor

@Mergifyio requeue

@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

@kumvprat
Copy link
Contributor

@Mergifyio queue

@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025 •
edited
Loading

queue

🛑 There are no queue conditions matching

There are queue conditions defined in the configuration, but none matches. The pull request has not been embarked.

Details:

  • Queue default-merge:
  • check-success=validate-pr
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • -approved-reviews-by~=author
  • -closed
  • -label~=(blocked|do-not-merge)
  • -merged
  • -title~=(WIP|wip)
  • check-success=build
  • label~=no-squash
  • any of:
    • -label~=pr/needs-integration-tests-deployment
    • check-success=integration_test_deployment
  • Queue priority-squash:
  • -label~=(blocked|do-not-merge|no-squash)
  • check-success=validate-pr
  • label~=priority-pr
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • -approved-reviews-by~=author
  • -closed
  • -merged
  • -title~=(WIP|wip)
  • base!=release
  • check-success=build
  • any of:
    • -label~=pr/needs-integration-tests-deployment
    • check-success=integration_test_deployment
  • Queue default-squash:
  • -label~=(blocked|do-not-merge|no-squash|priority-pr)
  • check-success=validate-pr
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • -approved-reviews-by~=author
  • -closed
  • -merged
  • -title~=(WIP|wip)
  • base!=release
  • check-success=build
  • any of:
    • -label~=pr/needs-integration-tests-deployment
    • check-success=integration_test_deployment

@mergify mergify bot added the queued label Oct 14, 2025
@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #35740 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: Required status check "validate-pr" is queued.).

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify mergify bot removed the queued label Oct 14, 2025
@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025

Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork).

@kumvprat
Copy link
Contributor

@Mergifyio requeue

@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

@kumvprat
Copy link
Contributor

@Mergifyio queue

@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025 •
edited
Loading

queue

🛑 There are no queue conditions matching

There are queue conditions defined in the configuration, but none matches. The pull request has not been embarked.

Details:

  • Queue default-merge:
  • check-success=validate-pr
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • -approved-reviews-by~=author
  • -closed
  • -label~=(blocked|do-not-merge)
  • -merged
  • -title~=(WIP|wip)
  • check-success=build
  • label~=no-squash
  • any of:
    • -label~=pr/needs-integration-tests-deployment
    • check-success=integration_test_deployment
  • Queue priority-squash:
  • -label~=(blocked|do-not-merge|no-squash)
  • check-success=validate-pr
  • label~=priority-pr
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • -approved-reviews-by~=author
  • -closed
  • -merged
  • -title~=(WIP|wip)
  • base!=release
  • check-success=build
  • any of:
    • -label~=pr/needs-integration-tests-deployment
    • check-success=integration_test_deployment
  • Queue default-squash:
  • -label~=(blocked|do-not-merge|no-squash|priority-pr)
  • check-success=validate-pr
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • -approved-reviews-by~=author
  • -closed
  • -merged
  • -title~=(WIP|wip)
  • base!=release
  • check-success=build
  • any of:
    • -label~=pr/needs-integration-tests-deployment
    • check-success=integration_test_deployment

@mergify mergify bot added the queued label Oct 14, 2025
@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #35740 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: Required status check "validate-pr" is queued.).

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify mergify bot removed the queued label Oct 14, 2025
@aws-cdk-automation aws-cdk-automation removed the pr/needs-maintainer-review This PR needs a review from a Core Team Member label Oct 14, 2025
@kumvprat
Copy link
Contributor

@Mergifyio requeue

@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025

Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify mergify bot added the queued label Oct 14, 2025
@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #35740 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: Required status check "validate-pr" is queued.).

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify mergify bot removed the queued label Oct 14, 2025
@mergify Mergify
Copy link
Contributor

mergify bot commented Oct 14, 2025

Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify mergify bot added the queued label Oct 14, 2025
@mergify mergify bot merged commit e64b72f into main Oct 14, 2025
106 of 108 checks passed
@mergify mergify bot deleted the merge-back/2.220.0 branch October 14, 2025 14:57
@mergify mergify bot removed the queued label Oct 14, 2025
@github-actions GitHub Actions
Copy link
Contributor

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@github-actions github-actions[bot] github-actions[bot] approved these changes

@kumvprat kumvprat kumvprat approved these changes

Assignees

No one assigned

Labels

auto-approve contribution/core This is a PR that came from AWS. p2 pr/no-squash This PR should be merged instead of squash-merging it

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@aws-cdk-automation @kumvprat