chore(release): 2.222.0 #35897

aws-cdk-automation · 2025-10-30T12:50:54Z

### Issue # (if applicable) Closes #<issue number here>. ### Reason for this change The readme was incorrectly showing that the default capacity is managed node group, but this is not the case in v2. in V2 the default is EKS auto mode, so the readme was updated to show the current default as the architecture, with some clarification on the other possible capacity modes. ### Description of changes Updated the readme to reflect the state of eks v2. ### Describe any new or updated permissions being added None ### Description of how you validated changes None ### Checklist - [X] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

#35783) ### Issue # (if applicable) Closes #35699 Related to: #35742 ### Reason for this change CfnClusterCapacityProviderAssociations is not needed when using only managed instances as a capacity provider, but it was being created anyway with empty values. It is needed if default capacity providers are set, or the capacity provider is not of the managed instances type. ### Description of changes Removed the `clusterScopedCapacityProviderNames` check when creating CfnClusterCapacityProviderAssociations. Destructive changes: CfnClusterCapacityProviderAssociations will be deleted if user does not provide default capacity providers or default fargate and uses only ManagedInstancesCapacityProvider. ### Describe any new or updated permissions being added None ### Description of how you validated changes ### Checklist - [X] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

### Issue # (if applicable) Closes #<issue number here>. ### Reason for this change ### Description of changes Move EKS v2 Alpha to developer preview ### Describe any new or updated permissions being added None ### Description of how you validated changes N/A ### Checklist - [X] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

See [CHANGELOG](https://github.com/aws/aws-cdk/blob/merge-back/2.221.0/CHANGELOG.md)

### Issue # (if applicable) Closes #32923. ### Reason for this change To support express brokers. ### Description of changes Add `express` property and validations about express limitations. ### Describe any new or updated permissions being added N/A ### Description of how you validated changes Add unit tests and an integ test. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

Very nit fix, I happened to notice ;) ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

This PR updates the enum values for ec2.

### Reason for this change There is a rosetta error due to a missing dependency. ### Description of changes Added dependency. ### Describe any new or updated permissions being added No new permissions added ### Description of how you validated changes Tested locally. Rosetta process succeeds. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

### Reason for this change Name was incorrectly configured. ### Description of changes Name is fixed. ### Describe any new or updated permissions being added No new permissions are added. ### Description of how you validated changes Check works on my fork using the mergify dashboard. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

…nation (#35762) ### Issue # (if applicable) Related to #35729. ### Reason for this change A PassRole policy is created whenever a cloudwatch destination is setup for a VPC flow destination. This is not needed as indicated from the [VPC flow docs](https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs-iam-role.html). ### Description of changes Removed policy. ### Describe any new or updated permissions being added PassRole policy is removed. ### Description of how you validated changes Unit tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

…nvironment (#35817) Previously, `construct.env` was declared in the `IResource` interface. Downside is that `IResource` also: - requires providing `stack: Stack` (which is a bit pointless to begin with since we can always call `Stack.of(x)`); and - `applyRemovalPolicy()` which doesn't belong on this interface but now is required to implement. Therefore, we extract `IResource#env` out to its own interface, `IEnvironmentAware`; make `IXxxRef` extend that interface, simplify `IResourceWithPolicy` to only be `IEnvironmentAware` and not an entire `IResource`. Lessening the requirements on `IResourceWithPolicy` also lessens its guarantees, which makes that a breaking change. In order to make this code change, we do the following: - Introduce `IResourceWithPolicyV2` to be the version of `IResourceWithPolicy` we should have had. - Accept `IResourceWithPolicyV2` everywhere - Make `IResourceWithPolicy` extend `IResourcWithPolicyV2` ``` ┌──────────────────────────┐ │ IEnvironmentAware │ └──────────────────────────┘ ▲ ┌───────────────────┴────────────────────┐ │ │ ┌──────────────────────────┐ ┌──────────────────────────┐ │ IResourceWithPolicyV2 │ │ IResource │ └──────────────────────────┘ └──────────────────────────┘ ▲ ▲ └──────────────────┬────────────────────┘ │ ┌──────────────────────────┐ │ IResourceWithPolicy │ └──────────────────────────┘ ``` ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

This is a revert of #35770; `jsii-pacmak` doesn't generate correct Go code for cross-module type intersections. Fixes #35862.

…by default (under feature flag) (#34675) ### Issue # (if applicable) Closes #34606. ### Reason for this change Currently, CDK's L2 constructs allow setting security groups for NLBs, but this requires explicit configuration. ```ts declare const sg1: ec2.ISecurityGroup; const lb = new elbv2.NetworkLoadBalancer(this, 'LB', { vpc, securityGroups: [sg1], // configure SG explicitly }); ``` This was not originally intended - NLB security group support was implemented later, and the current specification exists to maintain backward compatibility. #27978 #28494 However, when comparing NLBs without security groups to NLBs with security groups configured, the latter has significantly more advantages. Furthermore, once an NLB is created without security groups, it's impossible to add security group configuration later. Therefore, I propose using feature flags to make security group configuration the default for NLBs in CDK. ### Description of changes - Add `@aws-cdk/aws-elasticloadbalancingv2:networkLoadBalancerWithSecurityGroupByDefault` feature flag - Create security groups by default when feature flags are enabled ### Describe any new or updated permissions being added None ### Description of how you validated changes Add both unit and integ tests ### Other information [This implementation](#34606 (comment)) was also proposed in the issue, but it was not implemented because it was difficult to detect when referenced from other Connectables as follows case2. ```ts declare const nlb: elbv2.INetworkLoadBalancer; declare const other: IConnectable; // case1 nlb.connections.allowTo(other, ec2.Port.tcp(1234)); // case2 other.connections.allowTo(nlb, ec2.Port.tcp(2181)); ``` ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

…ose's `IDeliveryStream` (#33798) ### Issue # (if applicable) Related to #33757 and #33758 ### Reason for this change The module has the `KinesisFirehoseStreamV2` target class for Firehose delivery stream. But it has following issues: - Kinesis Data Firehose is now Amazon Data Firehose. Therefore the class should not be called Kinesis. Also, KinesisFirehoseStream is confusable with Kinesis Data Stream. - The constructor receives internally defined `IDeliveryStream` which is a subset of `aws_kinesisfirehose.IDeliveryStream` without inheritance. This may cause jsii type compatibility problem. ### Description of changes - Added a new `FirehoseDeliveryStream` target class derived from `KinesisFirehoseStreamV2` but receives `aws_kinesisfirehose.IDeliveryStream` instead. - Deprecated `KinesisFirehoseStreamV2` and internal `IDeliveryStream`. - Added missing unit tests for `FirehoseDeliveryStream` - Updated the integ test to use `FirehoseDeliveryStream` and assertions. - Added an missing README entry refers Amazon Data Firehose. ### Describe any new or updated permissions being added N/A - `FirehoseDeliveryStream` adds same permissions as `KinesisFirehoseStreamV2` ### Description of how you validated changes Unit tests and integ test. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

### Issue # (if applicable) Closes #35062. ### Reason for this change The `addToResourcePolicy()` method for DynamoDB tables had no effect - it was not adding resource policies to the synthesized CloudFormation template. Users calling `table.addToResourcePolicy()` found that their policies were ignored, forcing them to use insecure workarounds. ### Description of changes Fixed the `addToResourcePolicy()` method to properly update the CloudFormation table's resource policy: - **Fixed core bug**: Added missing `this.table.resourcePolicy = { policyDocument: this.resourcePolicy }` line in `addToResourcePolicy()` method - **Restored intended functionality**: Resource policies now appear in synthesized CloudFormation templates - **Applied to both Table V1 and V2**: Consistent behavior across all DynamoDB table constructs - **Avoids circular dependencies**: Uses wildcard resources (`*`) pattern to prevent CloudFormation circular dependency issues with auto-generated table names - **Added comprehensive tests**: 5 new tests covering both wildcard and scoped resource scenarios - **Updated README.md**: Completely rewrote `addToResourcePolicy` documentation: - Removed problematic examples that would create circular dependencies - Added correct wildcard resource pattern following KMS approach - Documented the CloudFormation limitation and workarounds - Provided clear examples for both standard and scoped resource policies **Before** (broken): ```typescript // This had no effect - policy was ignored table.addToResourcePolicy(new iam.PolicyStatement({ actions: ['dynamodb:GetItem'], principals: [new iam.AccountRootPrincipal()], resources: [table.tableArn], // This would also create circular dependency })); // CloudFormation template: No ResourcePolicy property ``` **After** (fixed): ```typescript // Now works correctly - policy appears in CloudFormation table.addToResourcePolicy(new iam.PolicyStatement({ actions: ['dynamodb:GetItem'], principals: [new iam.AccountRootPrincipal()], resources: ['*'], // Wildcard avoids circular dependency (KMS pattern) })); // CloudFormation template: ResourcePolicy.PolicyDocument properly set ``` **For scoped resources** (requires explicit table name): ```typescript const table = new dynamodb.Table(this, 'MyTable', { tableName: 'my-explicit-table-name', // Explicit name enables scoped resources partitionKey: { name: 'id', type: dynamodb.AttributeType.STRING }, }); table.addToResourcePolicy(new iam.PolicyStatement({ actions: ['dynamodb:GetItem'], principals: [new iam.AccountRootPrincipal()], resources: [ Fn.sub('arn:aws:dynamodb:${AWS::Region}:${AWS::AccountId}:table/my-explicit-table-name') ], })); ``` **Architecture Note**: DynamoDB tables use inline `ResourcePolicy` properties (like KMS keys) rather than separate policy resources. Due to CloudFormation's circular dependency limitations, resource policies must use wildcard resources (`*`) when table names are auto-generated, or explicit table names must be specified for scoped resources. ### Describe any new or updated permissions being added N/A - No new IAM permissions required. This change only affects how existing resource policies are structured. ### Description of how you validated changes - **Unit tests**: Added new `addToResourcePolicy` tests: - Standard wildcard resource usage (`resources: ['*']`) - Explicit table name workaround for scoped resources - Comprehensive limitation documentation - **Integration tests**: Added comprehensive integration test covering both wildcard and scoped resource patterns - **Full test suite**: All DynamoDB unit tests pass, confirming no regressions - **CloudFormation validation**: Verified synthesis works without circular dependency errors - **Deployment testing**: Confirmed resource policies are properly applied at deployment time ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

This re-applies #35770 (which was reverted in #35871). Contains an upgrade to a fixed version of `jsii-pacmak`. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

This PR updates the enum values for ecs.

### Issue # (if applicable) Related to aws/aws-cdk-rfcs#825 ### Reason for this change Adding a new alpha package for Amazon Bedrock AgentCore and add support for memory. ### Description of changes - Create a new alpha package - Add L2 constructs for memory - Add documentation - Add tests ### Describe any new or updated permissions being added Using permissions for agent core defined in https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonbedrockagentcore.html ### Description of how you validated changes Unit tests, integration tests, manual tests ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

This applies the code for L1 resource relationships, originally applied in #35713 and reverted in #35832. The reason is that another PR is also making changes in this area, branched in between the original application and its revert, and is now experiencing severe merge conflicts. In this PR, reintroduce the large refactorings made in the original PR, but disable their application by making the list of services we apply the relationships to empty. ```ts export const RELATIONSHIP_SERVICES: string[] = []; ``` There were some changes to L2s in the original PR that are not included in this PR; they will need to be reapplied when restoring the feature. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

… instead of string identifiers (#35860) ### Issue # (if applicable) Closes #35854 . ### Reason for this change Improve the Cognito authorizer configuration by accepting Cognito construct references instead of string identifiers, providing better type safety and integration with the CDK ecosystem. Additionally, add support for multi-clients. ### Description of changes - Enhanced `RuntimeAuthorizerConfiguration.usingCognito()` to accept `IUserPool` and `IUserPoolClient` constructs instead of string parameters - Added support for multiple Cognito clients through an array parameter The implementation now provides better CDK integration and type safety by using construct references rather than raw string identifiers. ### Describe any new or updated permissions being added N/A ### Description of how you validated changes Add unit tests and integ test. BREAKING CHANGE: The signature of `RuntimeAuthorizerConfiguration.usingCognito()` has changed to accept IUserPool and IUserPoolClient constructs instead of string parameters, and now supports multiple clients. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

Newly supported protocol. https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-bedrockagentcore-runtime.html#cfn-bedrockagentcore-runtime-protocolconfiguration ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

…roys and recreates policies on every deployment (#35842) ### Issue # (if applicable) Closes #35844 ### Reason for this change The current `addToRolePolicy` for Runtime with imported role destroys and recreates policies on every deployment. The reason is that `Date.now()` is used for a construct ID of a new Policy in the situation: https://github.com/aws/aws-cdk/blob/v2.221.0/packages/%40aws-cdk/aws-bedrock-agentcore-alpha/agentcore/runtime/runtime-base.ts#L253 ```ts public addToRolePolicy(statement: iam.PolicyStatement): IBedrockAgentRuntime { // Check if role is a concrete Role instance if (this.role instanceof iam.Role) { this.role.addToPolicy(statement); } else { // For imported roles (IRole), we need to attach via a new policy const policy = new iam.Policy(this, `CustomPolicy${Date.now()}`, { statements: [statement], }); ``` #### Reproduction 1. Deploy your stack with the following CDK code: ```ts const app = new cdk.App(); const stack = new cdk.Stack(app, 'aws-cdk-bedrock-agentcore-runtime-with-imported-role'); const runtimeArtifact = agentcore.AgentRuntimeArtifact.fromAsset( path.join(__dirname, 'testArtifact'), ); const role = new iam.Role(stack, 'ExecutionRole', { assumedBy: new iam.ServicePrincipal('bedrock-agentcore.amazonaws.com'), }); const imported = iam.Role.fromRoleArn(stack, 'ImportedRole', role.roleArn); const runtime = new agentcore.Runtime(stack, 'TestRuntime', { runtimeName: 'integ_test_runtime', agentRuntimeArtifact: runtimeArtifact, executionRole: imported, }); runtime.addToRolePolicy(new iam.PolicyStatement({ actions: ['dynamodb:Query'], resources: ['arn:aws:dynamodb:us-east-1:123456789012:table/my-table'], })); ``` 2. Deploy or diff the stack with the same CDK code again. 3. The change will occur: ``` [-] AWS::IAM::Policy TestRuntimeCustomPolicy1761380931769044921D2 destroy [+] AWS::IAM::Policy TestRuntimeCustomPolicy1761381522330E0DC0D40 ``` ### Description of changes Use `addToPrincipalPolicy` directly instead. ### Describe any new or updated permissions being added ### Description of how you validated changes Both unit tests and an integ test. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

Ref: [TwelveLabs’ Marengo Embed 3.0 for advanced video understanding now in Amazon Bedrock](https://aws.amazon.com/about-aws/whats-new/2025/10/twelvelabs-marengo3-embed-amazon-bedrock/) ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

…#35894) When anyone modifies a workflow, mergify will fail to update the PR via a merge commit because of Github security which makes it look like Mergify is updating the workflows, which is disallowed without the `workflows` permission. This switches to rebase by default.

…xisting roles (#35123) ### Issue # (if applicable) Closes #35120 ### Reason for this change Dependency on permission was only applied to new roles, not to existing roles. ### Description of changes The dependency on permission now applies to both new and existing roles. ### Describe any new or updated permissions being added Not applicable. ### Description of how you validated changes I've added an integration test for an agent with an existing/custom role attached to it. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

mergify · 2025-10-30T13:31:46Z

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).

github-actions · 2025-10-30T14:40:05Z

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.

aemada-aws and others added 28 commits October 24, 2025 13:13

Merge branch 'main' into merge-back/2.221.0

003f20d

chore(merge-back): 2.221.0 (#35840)

efefbb3

See [CHANGELOG](https://github.com/aws/aws-cdk/blob/merge-back/2.221.0/CHANGELOG.md)

chore(ec2): add new enum values for ec2 (#35805)

a7a6b40

This PR updates the enum values for ec2.

fix: compilation failure in Go (#35871)

5e4f603

This is a revert of #35770; `jsii-pacmak` doesn't generate correct Go code for cross-module type intersections. Fixes #35862.

chore(ecs): add new enum values for ecs (#35806)

9bec236

This PR updates the enum values for ecs.

chore(release): 2.222.0

7da939a

aws-cdk-automation requested a review from a team as a code owner October 30, 2025 12:50

aws-cdk-automation added the auto-approve label Oct 30, 2025

aws-cdk-automation added the pr/no-squash This PR should be merged instead of squash-merging it label Oct 30, 2025

aws-cdk-automation requested a review from a team October 30, 2025 12:51

github-actions bot added the p2 label Oct 30, 2025

github-actions bot approved these changes Oct 30, 2025

View reviewed changes

mergify bot added the contribution/core This is a PR that came from AWS. label Oct 30, 2025

aws-cdk-automation requested a deployment to test-pipeline October 30, 2025 12:51 — with GitHub Actions Waiting

aws-cdk-automation requested a deployment to test-pipeline October 30, 2025 12:52 — with GitHub Actions Waiting

mergify bot requested a deployment to test-pipeline October 30, 2025 12:52 Waiting

aemada-aws closed this Oct 30, 2025

aemada-aws deleted the bump/2.222.0 branch October 30, 2025 14:40

github-actions bot locked as resolved and limited conversation to collaborators Oct 30, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(release): 2.222.0 #35897

chore(release): 2.222.0 #35897

Uh oh!

aws-cdk-automation commented Oct 30, 2025 •

edited

Loading

Uh oh!

mergify bot commented Oct 30, 2025

Uh oh!

github-actions bot commented Oct 30, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

11 participants

chore(release): 2.222.0 #35897

chore(release): 2.222.0 #35897

Uh oh!

Conversation

aws-cdk-automation commented Oct 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mergify bot commented Oct 30, 2025

Uh oh!

github-actions bot commented Oct 30, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

11 participants

aws-cdk-automation commented Oct 30, 2025 •

edited

Loading