Skip to content

chore(deps): update dependency aws-cdk-lib to v2.195.0 #1359

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

Open
wants to merge 1 commit into
base: saga
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 27, 2025

This PR contains the following updates:

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

Release Notes

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

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

v2.194.0

Compare Source

Features

Alpha modules (2.194.0-alpha.0)

v2.193.0

Compare Source

Features
Bug Fixes

Alpha modules (2.193.0-alpha.0)

Features
  • pipes-targets-alpha: support Amazon Data Firehose target (#​33860) (ebf1ea2)

v2.192.0

Compare Source

Features
Bug Fixes

Alpha modules (2.192.0-alpha.0)

Features
  • applicationsignals-alpha: introduce Application Signals L2 constructs (#​32931) (e7a6e14)

v2.191.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.
  • neptune-alpha: Id attribute is being removed from the
    AWS::Neptune::DBClusterParameterGroup and AWS::Neptune::DBParameterGroup
    resources
  • aws-launchwizard: specifications prop moved from required to
    optional in CfnDeployment
  • aws-ses: attribute attribute moved from required to optional in
    RuleBooleanToEvaluateProperty
Features
  • cloudformation: update L1 CloudFormation resource definitions (#​34207) (adfa416)
  • update L1 CloudFormation resource definitions (e3483c2)
  • codebuild: add additional build images for lambda (#​34197) (5a265d1)
  • rds: add Aurora MySQL versions 2.12.4, 3.08.2 (#​34045) (1dd993e)

Alpha modules (2.191.0-alpha.0)
Features

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 Apr 27, 2025
@renovate renovate bot enabled auto-merge (squash) April 27, 2025 23:17
Copy link
Contributor Author

renovate bot commented Apr 27, 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: @bifravst/[email protected]
npm error node_modules/@bifravst/aws-ssm-settings-helpers
npm error   @bifravst/aws-ssm-settings-helpers@"1.2.130" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @bifravst/aws-ssm-settings-helpers@"^1.2.138" 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.228" 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-09T00_15_39_799Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-09T00_15_39_799Z-debug-0.log

@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch 4 times, most recently from b20ca10 to 4394989 Compare May 2, 2025 04:06
@renovate renovate bot changed the title chore(deps): update dependency aws-cdk-lib to v2.192.0 chore(deps): update dependency aws-cdk-lib to v2.194.0 May 2, 2025
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch 5 times, most recently from 9318aa3 to a522c3b Compare May 4, 2025 11:13
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch from a522c3b to d4306b2 Compare May 9, 2025 00:15
@renovate renovate bot changed the title chore(deps): update dependency aws-cdk-lib to v2.194.0 chore(deps): update dependency aws-cdk-lib to v2.195.0 May 9, 2025
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