From 53e56d4ac207ba4307fe02af86cf66d89976026a Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Fri, 19 Jun 2026 05:59:13 +0000 Subject: [PATCH] chore: version packages --- .changeset/lambda-pc-on-version.md | 10 ---------- packages/aws/CHANGELOG.md | 10 ++++++++++ packages/aws/package.json | 2 +- packages/cdk-utils/CHANGELOG.md | 15 +++++++++++++++ packages/cdk-utils/package.json | 2 +- 5 files changed, 27 insertions(+), 12 deletions(-) delete mode 100644 .changeset/lambda-pc-on-version.md diff --git a/.changeset/lambda-pc-on-version.md b/.changeset/lambda-pc-on-version.md deleted file mode 100644 index 9aac4f27b..000000000 --- a/.changeset/lambda-pc-on-version.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -'@gradientedge/cdk-utils-aws': minor -'@gradientedge/cdk-utils': minor ---- - -Add `ProvisionedConcurrencyProps.onVersion` flag. When `true`, provisioned concurrency and its auto-scaling target attach to the published function version (`function::`) instead of the alias (`function::`). - -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. diff --git a/packages/aws/CHANGELOG.md b/packages/aws/CHANGELOG.md index 9182e2b29..719ae265e 100644 --- a/packages/aws/CHANGELOG.md +++ b/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::`) instead of the alias (`function::`). + + 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 diff --git a/packages/aws/package.json b/packages/aws/package.json index ea41f819e..34cbea5ee 100644 --- a/packages/aws/package.json +++ b/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", diff --git a/packages/cdk-utils/CHANGELOG.md b/packages/cdk-utils/CHANGELOG.md index 31b24b4dd..4f5e18e4a 100644 --- a/packages/cdk-utils/CHANGELOG.md +++ b/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::`) instead of the alias (`function::`). + + 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 diff --git a/packages/cdk-utils/package.json b/packages/cdk-utils/package.json index 0d4eeb1dc..580fd9fd4 100644 --- a/packages/cdk-utils/package.json +++ b/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",