aws-cdk 2.1140.0 → 2.1141.0

package/README.md

@@ -291,7 +291,43 @@ You can have multiple stacks in a cdk app. An example can be found in [how to cr
 
 In order to deploy them, you can list the stacks you want to deploy. If your application contains pipeline stacks, the `cdk list` command will show stack names as paths, showing where they are in the pipeline hierarchy (e.g., `PipelineStack`, `PipelineStack/Prod`, `PipelineStack/Prod/MyService` etc).
 
-If you want to deploy all of them, you can use the flag `--all` or the wildcard `*` to deploy all stacks in an app. Please note that, if you have a hierarchy of stacks as described above, `--all` and `*` will only match the stacks on the top level. If you want to match all the stacks in the hierarchy, use `**`. You can also combine these patterns. For example, if you want to deploy all stacks in the `Prod` stage, you can use `cdk deploy PipelineStack/Prod/**`.
+To deploy every stack in the app, use the `--all` flag or the wildcard `*`.
+If your app has stacks inside stages, keep in mind how far each wildcard reaches:
+
+- `*` matches one level, so it only picks up top-level stacks (same as `--all`)
+- `**` matches any number of levels, so it picks up stacks at every depth
+
+You can also combine these patterns.
+For example, to deploy everything inside the `Prod` stage of a pipeline:
+
+```console
+cdk deploy 'PipelineStack/Prod/**'
+```
+
+##### Excluding stacks
+
+Put a `!` in front of a pattern to leave those stacks out.
+Wrap the pattern in quotes so your shell leaves the `!` alone.
+
+Every stack except `NlbStack`:
+
+```
+cdk deploy '!NlbStack'
+```
+
+Everything under `Prod`, except the canary:
+
+```
+cdk deploy 'PipelineStack/Prod/**' '!PipelineStack/Prod/Canary'
+```
+
+CDK picks the stacks your normal patterns match, then drops the ones your `!` patterns match.
+If you only pass `!` patterns, they apply to every stack in the app.
+`--all` doesn't work together with patterns, so use `**` instead.
+An excluded stack still deploys if a selected stack needs it — add `--exclusively` (`-e`) to skip dependencies.
+And `!(...)` is shell syntax, not a CDK exclusion.
+
+##### Deploying stacks in parallel
 
 `--concurrency N` allows deploying multiple stacks in parallel while respecting inter-stack dependencies to speed up deployments. It does not protect against CloudFormation and other AWS account rate limiting.
 

package/THIRD_PARTY_LICENSES

@@ -5155,7 +5155,7 @@ Apache License
 
 ----------------
 
-** @aws-sdk/credential-provider-node@3.972.81 - https://www.npmjs.com/package/@aws-sdk/credential-provider-node/v/3.972.81 | Apache-2.0
+** @aws-sdk/credential-provider-node@3.972.82 - https://www.npmjs.com/package/@aws-sdk/credential-provider-node/v/3.972.82 | Apache-2.0
 Apache License
                            Version 2.0, January 2004
                         http://www.apache.org/licenses/
@@ -5975,7 +5975,7 @@ Apache License
 
 ----------------
 
-** @aws-sdk/credential-providers@3.1120.0 - https://www.npmjs.com/package/@aws-sdk/credential-providers/v/3.1120.0 | Apache-2.0
+** @aws-sdk/credential-providers@3.1126.0 - https://www.npmjs.com/package/@aws-sdk/credential-providers/v/3.1126.0 | Apache-2.0
 Apache License
                            Version 2.0, January 2004
                         http://www.apache.org/licenses/
@@ -10936,7 +10936,7 @@ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI
 
 ----------------
 
-** cdk-from-cfn@0.327.0 - https://www.npmjs.com/package/cdk-from-cfn/v/0.327.0 | MIT OR Apache-2.0
+** cdk-from-cfn@0.329.0 - https://www.npmjs.com/package/cdk-from-cfn/v/0.329.0 | MIT OR Apache-2.0
 
 ----------------
 

package/build-info.json

@@ -1,4 +1,4 @@
 {
-  "comment": "Generated at 2026-09-04T14:28:35Z by generate.sh",
-  "commit": "5b77563"
+  "comment": "Generated at 2026-09-09T14:09:44Z by generate.sh",
+  "commit": "c07d251"
 }

package/lib/cli/cdk-toolkit.d.ts

@@ -1,5 +1,5 @@
 import { RequireApproval } from '@aws-cdk/cloud-assembly-schema';
-import type { DeploymentMethod, DiagnoseOptions, PublishAssetsOptions, StackSelector, ToolkitOptions, ValidateOptions } from '@aws-cdk/toolkit-lib';
+import type { DeploymentMethod, DiagnoseOptions, PublishAssetsOptions, StackSelector, SynthOptions as ToolkitSynthOptions, ToolkitOptions, ValidateOptions } from '@aws-cdk/toolkit-lib';
 import { Toolkit } from '@aws-cdk/toolkit-lib';
 import { CliIoHost } from './io-host';
 import type { Configuration } from './user-configuration';
@@ -152,6 +152,14 @@ export declare class CdkToolkit {
      * should be supplied, where the templates will be written.
      */
     synth(options: SynthOptions): Promise<any>;
+    /**
+     * Continuously synthesize the project, re-synthesizing on every file change.
+     * Never deploys, and never prints templates to stdout.
+     *
+     * The files to observe are configured with the "watch" key of `cdk.json`,
+     * exactly like `cdk deploy --watch`.
+     */
+    synthWatch(options: ToolkitSynthOptions): Promise<void>;
     /**
      * Bootstrap the CDK Toolkit stack in the accounts used by the specified stack(s).
      *