Skip to content

chore(merge-back): 2.243.0#37226

Merged
mergify[bot] merged 4 commits into
mainfrom
merge-back/2.243.0
Mar 12, 2026
Merged

chore(merge-back): 2.243.0#37226
mergify[bot] merged 4 commits into
mainfrom
merge-back/2.243.0

Conversation

@aws-cdk-automation
Copy link
Copy Markdown
Collaborator

@aws-cdk-automation aws-cdk-automation commented Mar 11, 2026 •
edited
Loading

See CHANGELOG

@aws-cdk-automation aws-cdk-automation added auto-approve pr/no-squash This PR should be merged instead of squash-merging it labels Mar 11, 2026
@github-actions github-actions Bot added the p2 label Mar 11, 2026
@aws-cdk-automation aws-cdk-automation requested a review from a team March 11, 2026 16:21
@aws-cdk-automation aws-cdk-automation added the pr/needs-community-review This PR needs a review from a Trusted Community Member or Core Team Member. label Mar 11, 2026
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Mar 11, 2026

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
Copy link
Copy Markdown
Contributor

mergify Bot commented Mar 11, 2026 •
edited
Loading

Merge Queue Status

  • ✅ Entered queue — 2026-03-11 16:52 UTC · Rule: default-merge
  • ✅ Checks started · in-place
  • 🚫 Left the queue — 2026-03-11 17:19 UTC · at 59f0241e9f6d1fcbdb81871c199a34fd5b85f27a

This pull request spent 27 minutes 30 seconds in the queue, with no time running CI.

Required conditions to merge
  • any of [🛡 GitHub branch protection]:
    • check-neutral = build
    • check-skipped = build
    • check-success = build
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = validate-pr
    • check-neutral = validate-pr
    • check-skipped = validate-pr

Reason

The merge conditions cannot be satisfied due to failing checks

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, 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 queue comment.

@pahud pahud mentioned this pull request Mar 11, 2026
Open
@leonmk-aws leonmk-aws added the pr/do-not-merge This PR should not be merged at this time. label Mar 11, 2026
@leonmk-aws leonmk-aws removed the pr/do-not-merge This PR should not be merged at this time. label Mar 12, 2026
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Mar 12, 2026

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
Copy link
Copy Markdown
Contributor

mergify Bot commented Mar 12, 2026 •
edited
Loading

Merge Queue Status

  • ✅ Entered queue — 2026-03-12 09:45 UTC · Rule: default-merge
  • ✅ Checks passed · in-place
  • ✅ Merged — 2026-03-12 10:16 UTC · at ed8a80f3b8f25000426f7bbfd03f6ba3bd510ed4

This pull request spent 30 minutes 46 seconds in the queue, including 30 minutes 34 seconds running CI.

Required conditions to merge
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = validate-pr
    • check-neutral = validate-pr
    • check-skipped = validate-pr
  • any of [🛡 GitHub branch protection]:
    • check-success = build
    • check-neutral = build
    • check-skipped = build

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Mar 12, 2026

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 merged commit 8e13735 into main Mar 12, 2026
18 of 19 checks passed
@mergify mergify Bot deleted the merge-back/2.243.0 branch March 12, 2026 10:16
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Mar 12, 2026

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 Mar 12, 2026
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

Assignees

No one assigned

Labels

auto-approve p2 pr/needs-community-review This PR needs a review from a Trusted Community Member or Core Team Member. 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 @leonmk-aws