Describe the bug

Up to version 2.179.0 the output of cdk deploy --no-execute would contain the CloudFormation ChangeSet ARN. I noticed this does not happen from 2.1000 on. Is there another way of getting the ARN or is this a bug?

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Version

2.179.0

Expected Behavior

With 2.179 the output when using --no-execute looks like:

✨  Synthesis time: 0.34s

XXXX: deploying... [1/1]
XXXX: creating CloudFormation changeset...
Changeset XXXXXXX created and waiting in review for manual execution (--no-execute)

 ✅  XXXXXXX

✨  Deployment time: 13.01s

Stack ARN:
XXXXXX

✨  Total time: 13.36s

Current Behavior

Output with 2.1001.0

✨  Synthesis time: 0.35s

XXXX: deploying... [1/1]
XXXX: creating CloudFormation changeset...

 ✅  XXXXXXX

✨  Deployment time: 17.04s

Stack ARN:
XXXXXXX

✨  Total time: 17.39s

Reproduction Steps

Deploy an app with the --no-execute parameter and compare stdout.

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.1001.0

Framework Version

No response

Node.js Version

v23.7.0

OS

macOS

Language

TypeScript

Language Version

No response

Other information

No response