Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 17, 2025

This PR contains the following updates:

Package Change Age Confidence
cdk (source) 2.1029.4 -> 2.1031.1 age confidence

Release Notes

aws/aws-cdk-cli (cdk)

v2.1031.1

Compare Source

2.1031.1 (2025-10-30)

v2.1031.0

Compare Source

2.1031.0 (2025-10-22)

v2.1030.0

Compare Source

2.1030.0 (2025-10-09)


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 Oct 17, 2025
@renovate renovate bot enabled auto-merge (squash) October 17, 2025 13:52
@renovate
Copy link
Contributor Author

renovate bot commented Oct 17, 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/map-backend@0.0.0-development
npm error Found: @aws-sdk/client-dynamodb@3.902.0
npm error node_modules/@aws-sdk/client-dynamodb
npm error   dev @aws-sdk/client-dynamodb@"3.902.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @aws-sdk/client-dynamodb@"^3.913.0" from @hello.nrfcloud.com/nrfcloud-api-helpers@6.0.388
npm error node_modules/@hello.nrfcloud.com/nrfcloud-api-helpers
npm error   @hello.nrfcloud.com/nrfcloud-api-helpers@"6.0.388" 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-11-08T21_13_26_110Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-08T21_13_26_110Z-debug-0.log

@renovate renovate bot force-pushed the renovate/cdk-2.x branch 3 times, most recently from d11690c to 6b4598b Compare October 21, 2025 00:13
@renovate renovate bot force-pushed the renovate/cdk-2.x branch from 6b4598b to 868c70f Compare October 25, 2025 15:43
@renovate renovate bot changed the title chore(deps): update dependency cdk to v2.1030.0 chore(deps): update dependency cdk to v2.1031.0 Oct 25, 2025
@renovate renovate bot force-pushed the renovate/cdk-2.x branch 8 times, most recently from 4611b7f to 5117b79 Compare October 26, 2025 22:07
@renovate renovate bot force-pushed the renovate/cdk-2.x branch from 5117b79 to 4c5d388 Compare November 8, 2025 11:54
@renovate renovate bot changed the title chore(deps): update dependency cdk to v2.1031.0 chore(deps): update dependency cdk to v2.1031.1 Nov 8, 2025
@renovate renovate bot force-pushed the renovate/cdk-2.x branch 2 times, most recently from 9253133 to bae8142 Compare November 8, 2025 16:27
@renovate renovate bot force-pushed the renovate/cdk-2.x branch from bae8142 to 9a00420 Compare November 8, 2025 21:13
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.

1 participant