Skip to content

Conversation

@ozelalisen
Copy link
Member

See CHANGELOG

@ozelalisen ozelalisen added the pr/no-squash This PR should be merged instead of squash-merging it label Nov 20, 2025
@aws-cdk-automation aws-cdk-automation requested a review from a team November 20, 2025 11:53
@github-actions github-actions bot added the p2 label Nov 20, 2025
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Nov 20, 2025
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(This review is outdated)

Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(This review is outdated)

@ozelalisen ozelalisen changed the title chore(release): 2.226.0 chore(release): 2.226.0 Nov 20, 2025
@aws-cdk-automation aws-cdk-automation dismissed stale reviews from themself November 20, 2025 11:56

Dismissing outdated PRLinter review.

@mergify
Copy link
Contributor

mergify bot commented Nov 20, 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
Copy link
Contributor

mergify bot commented Nov 20, 2025

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

Pull request #36128 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 "build" is in progress.).

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.

@ozelalisen
Copy link
Member Author

@Mergifyio requeue

@mergify
Copy link
Contributor

mergify bot commented Nov 20, 2025

requeue

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

@mergify mergify bot merged commit 73ea0c1 into v2-release Nov 20, 2025
94 of 95 checks passed
@mergify mergify bot deleted the new_v2.226.x_v2 branch November 20, 2025 12:40
@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 Nov 20, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

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

Development

Successfully merging this pull request may close these issues.

3 participants