Skip to content

chore(deps): update dependency aws-cdk-lib to v2.196.0 #701

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 19, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 11, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
aws-cdk-lib (source) 2.194.0 -> 2.196.0 age adoption passing confidence

Release Notes

aws/aws-cdk (aws-cdk-lib)

v2.196.0

Compare Source

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES
  • cloudformation: Some L1 resources experienced breaking changes due to updated CloudFormation resources. Please check the notes for each specific module for more information.
  • Logs: The type of property DeliveryDestinationPolicy of resource AWS::Logs::DeliveryDestination changed to be DestinationPolicy instead of JSON.
Features
Bug Fixes

Alpha modules (2.196.0-alpha.0)
Features
Bug Fixes
  • ec2: dual-stack vpc without private subnets creates EgressOnlyInternetGateway (under feature flag) (#​34437) (35e818b), closes #​30981
  • ec2-alpha: fix resource id references and tags for migration behind feature flag (#​34377) (aa73534)

v2.195.0

Compare Source

Features
Bug Fixes
  • codepipeline: allow both pullRequestFilter and pushFilter (#​34267) (1cac5a0), closes #​34253
  • route53-targets: beanstalk allow specifying hostedZoneId to support token endpoint with default value derived from stack region or endpointUrl (#​34122) (9e52752), closes #​31843
  • s3-notifications: add a key policy to trust S3 for notifications to an SNS topic encrypted with a KMS key (under feature flag) (#​33858) (1e87861), closes #​16271
Reverts

Alpha modules (2.195.0-alpha.0)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES
  • iot: By default, deviceDertificateAgeCheck is automatically enabled.
Features
Bug Fixes

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 renovate bot added dependencies help wanted Extra attention is needed labels May 11, 2025
@renovate renovate bot enabled auto-merge (squash) May 11, 2025 14:55
@renovate renovate bot added help wanted Extra attention is needed dependencies labels May 11, 2025
Copy link
Contributor Author

renovate bot commented May 11, 2025

⚠️ 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: @aws-sdk/[email protected]
npm error node_modules/@aws-sdk/client-dynamodb
npm error   dev @aws-sdk/client-dynamodb@"3.799.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @aws-sdk/client-dynamodb@"^3.812.0" from @hello.nrfcloud.com/[email protected]
npm error node_modules/@hello.nrfcloud.com/nrfcloud-api-helpers
npm error   @hello.nrfcloud.com/nrfcloud-api-helpers@"6.0.247" 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-05-19T21_10_48_526Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-19T21_10_48_526Z-debug-0.log

@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch 6 times, most recently from 8377d1a to e5fe15a Compare May 17, 2025 16:11
@renovate renovate bot changed the title chore(deps): update dependency aws-cdk-lib to v2.195.0 chore(deps): update dependency aws-cdk-lib to v2.196.0 May 17, 2025
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch 11 times, most recently from 731ee28 to a03ba45 Compare May 19, 2025 12:50
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch from a03ba45 to 90ee43c Compare May 19, 2025 21:10
@renovate renovate bot merged commit 611d7e4 into saga May 19, 2025
7 of 9 checks passed
@renovate renovate bot deleted the renovate/aws-cdk-monorepo branch May 19, 2025 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants