chore(deps): update dependency aws-cdk to v2.1022.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
aws-cdk (source)	2.1018.1 -> 2.1022.0

---

Release Notes

aws/aws-cdk-cli (aws-cdk)

v2.1022.0

Compare Source

2.1022.0 (2025-07-24)

Features

• cli: --no-version-reporting equals --no-telemetry for cli telemetry and library metadata exclusion (#​718) (d40bf52)
• cli: cli-telemetry status command (#​697) (666f1b9), closes #​631
• cli: send telemetry events to local file (#​631) (a6755f0)
• cli: telemetry event deploy (#​698) (d441f68), closes #​631

Bug Fixes

• cli: running --telemetry-file without the --unstable option creates a telemetry file (#​731) (cde4468)

v2.1021.0

Compare Source

2.1021.0 (2025-07-16)

Features

• "cdk flags" command reports active and missing feature flags (unstable) (#​699) (d62b991)
• diff shows moved resources (#​708) (6beac2b)
• modification is forbidden during a refactor (#​667) (66594fd)
• overrides to resolve mapping ambiguities (#​679) (fdec382)
• toolkit-lib: list action contains metadata (#​719) (d71960e), closes #​501

Bug Fixes

• integ-testing: add test that forces cdk-assets to use the Docker credentials helper (#​663) (1f7527b)
• upgrade to jsii & typescript 5.8 (#​693) (90579c3)

v2.1020.2

Compare Source

2.1020.2 (2025-07-03)

v2.1020.1

Compare Source

2.1020.1 (2025-07-02)

v2.1020.0

Compare Source

2.1020.0 (2025-07-01)

Features

• cli: telemetry opt-out command (#​579) (3b4d18e), closes #​575

v2.1019.2

Compare Source

2.1019.2 (2025-06-25)

Bug Fixes

• cdk-assets: fails installation when new dependencies are released (#​603) (6625d97)
• cli: logs entire environment (#​623) (639455e)

v2.1019.1

Compare Source

2.1019.1 (2025-06-19)

Bug Fixes

• revert "retain type of context values and not convert them to string" (#​630) (76ac13c)

v2.1019.0

Compare Source

2.1019.0 (2025-06-18)

Features

• cli: aws-cdk bundle is now targeting node18 (#​610) (bdf1f66)

Bug Fixes

• cli: retain type of context values and not convert them to string (#​595) (6250b39), closes #​30583

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @hello.nrfcloud.com/[email protected]
npm error Found: [email protected]
npm error node_modules/aws-cdk-lib
npm error   dev aws-cdk-lib@"2.201.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer aws-cdk-lib@"^2.204.0" from @bifravst/[email protected]
npm error node_modules/@bifravst/aws-ssm-settings-helpers
npm error   @bifravst/aws-ssm-settings-helpers@"1.2.169" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-07-28T18_16_40_138Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-07-28T18_16_40_138Z-debug-0.log