chore: version packages

packages/aws/CHANGELOG.md

@@ -1,5 +1,15 @@
 # @gradientedge/cdk-utils-aws
 
+## 2.22.0
+
+### Minor Changes
+
+- [#1110](https://github.com/gradientedge/cdk-utils/pull/1110) [`d650aa2`](https://github.com/gradientedge/cdk-utils/commit/d650aa2f0c65bf110888e1d6d8eb5444c488fb38) Thanks [@despock](https://github.com/despock)! - Add `ProvisionedConcurrencyProps.onVersion` flag. When `true`, provisioned concurrency and its auto-scaling target attach to the published function version (`function:<fn>:<version>`) instead of the alias (`function:<fn>:<aliasName>`).
+
+  This avoids a deploy-wedging trap: when PC is on the alias, every CFN alias update that changes `FunctionVersion` triggers Lambda's built-in canary behaviour (CFN sets `RoutingConfig.AdditionalVersionWeights` to keep traffic on the old version until PC allocates on the new one). If the new version's init fails (`FUNCTION_ERROR_INIT_FAILURE`), the routing weights persist at 100% on old and every subsequent deploy fails with `Invalid alias configuration for Provisioned Concurrency`. With PC on the version instead, alias updates are atomic, no routing weights are ever set, and the wedge can't happen.
+
+  Default is `false`; existing consumers are unaffected. Trade-off: ApplicationAutoScaling targets accumulate one per deploy (resource id embeds the version) — fine for normal cadence; regional soft limit is 2,500.
+
 ## 2.21.0
 
 ### Minor Changes

packages/aws/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gradientedge/cdk-utils-aws",
-  "version": "2.21.0",
+  "version": "2.22.0",
   "description": "AWS CDK utilities for @gradientedge/cdk-utils",
   "type": "module",
   "main": "dist/src/index.js",

packages/cdk-utils/CHANGELOG.md

@@ -1,5 +1,20 @@
 # @gradientedge/cdk-utils
 
+## 11.57.0
+
+### Minor Changes
+
+- [#1110](https://github.com/gradientedge/cdk-utils/pull/1110) [`d650aa2`](https://github.com/gradientedge/cdk-utils/commit/d650aa2f0c65bf110888e1d6d8eb5444c488fb38) Thanks [@despock](https://github.com/despock)! - Add `ProvisionedConcurrencyProps.onVersion` flag. When `true`, provisioned concurrency and its auto-scaling target attach to the published function version (`function:<fn>:<version>`) instead of the alias (`function:<fn>:<aliasName>`).
+
+  This avoids a deploy-wedging trap: when PC is on the alias, every CFN alias update that changes `FunctionVersion` triggers Lambda's built-in canary behaviour (CFN sets `RoutingConfig.AdditionalVersionWeights` to keep traffic on the old version until PC allocates on the new one). If the new version's init fails (`FUNCTION_ERROR_INIT_FAILURE`), the routing weights persist at 100% on old and every subsequent deploy fails with `Invalid alias configuration for Provisioned Concurrency`. With PC on the version instead, alias updates are atomic, no routing weights are ever set, and the wedge can't happen.
+
+  Default is `false`; existing consumers are unaffected. Trade-off: ApplicationAutoScaling targets accumulate one per deploy (resource id embeds the version) — fine for normal cadence; regional soft limit is 2,500.
+
+### Patch Changes
+
+- Updated dependencies [[`d650aa2`](https://github.com/gradientedge/cdk-utils/commit/d650aa2f0c65bf110888e1d6d8eb5444c488fb38)]:
+  - @gradientedge/cdk-utils-aws@2.22.0
+
 ## 11.56.0
 
 ### Minor Changes

packages/cdk-utils/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gradientedge/cdk-utils",
-  "version": "11.56.0",
+  "version": "11.57.0",
   "description": "Utilities for AWS CDK, Azure and Cloudflare Pulumi provisioning",
   "type": "module",
   "main": "dist/src/index.js",