Skip to content
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

chore(deps): update dependency @bifravst/aws-cdk-lambda-helpers to v3.1.19 #592

Merged
merged 1 commit into from
Mar 14, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 13, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@bifravst/aws-cdk-lambda-helpers 3.1.12 -> 3.1.19 age adoption passing confidence

Release Notes

bifravst/aws-cdk-lambda-helpers (@​bifravst/aws-cdk-lambda-helpers)

v3.1.19

Compare Source

Bug Fixes

v3.1.18

Compare Source

Bug Fixes
  • deps: update dependency aws-cdk-lib to ^2.184.1 (29b4acb)

v3.1.17

Compare Source

Bug Fixes

v3.1.16

Compare Source

Bug Fixes

v3.1.15

Compare Source

Bug Fixes

v3.1.14

Compare Source

Bug Fixes

v3.1.13

Compare Source

Bug Fixes

v3.1.12

Compare Source

Bug Fixes

v3.1.11

Compare Source

Bug Fixes

v3.1.10

Compare Source

Bug Fixes

v3.1.9

Compare Source

Bug Fixes

v3.1.8

Compare Source

Bug Fixes

v3.1.7

Compare Source

Bug Fixes

v3.1.6

Compare Source

Bug Fixes

v3.1.5

Compare Source

Bug Fixes

v3.1.4

Compare Source

Bug Fixes

v3.1.3

Compare Source

Bug Fixes
  • deps: update dependency aws-cdk-lib to ^2.181.1 (fea8185)

v3.1.2

Compare Source

Bug Fixes

v3.1.1

Compare Source

Bug Fixes

v3.1.0

Compare Source

Bug Fixes
Features
  • allow to set architecture (b97453e)

v3.0.47

Compare Source

Bug Fixes

v3.0.46

Compare Source

Bug Fixes

v3.0.45

Compare Source

Bug Fixes

v3.0.44

Compare Source

Bug Fixes

v3.0.43

Compare Source

Bug Fixes

v3.0.42

Compare Source

Bug Fixes

v3.0.41

Compare Source

Bug Fixes

v3.0.40

Compare Source

Bug Fixes

v3.0.39

Compare Source

Bug Fixes

v3.0.38

Compare Source

Bug Fixes

v3.0.37

Compare Source

Bug Fixes

v3.0.36

Compare Source

Bug Fixes
  • deps: update aws-cdk monorepo to ^2.178.2 (2886ecc)

v3.0.35

Compare Source

Bug Fixes

v3.0.34

Compare Source

Bug Fixes

v3.0.33

Compare Source

Bug Fixes

v3.0.32

Compare Source

Bug Fixes
  • deps: update aws-cdk monorepo to ^2.178.1 (bbf2423)

v3.0.31

Compare Source

Bug Fixes

v3.0.30

Compare Source

Bug Fixes

v3.0.29

Compare Source

Bug Fixes

v3.0.28

Compare Source

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.

Sorry, something went wrong.

@renovate renovate bot added dependencies help wanted Extra attention is needed labels Mar 13, 2025
@renovate renovate bot enabled auto-merge (squash) March 13, 2025 14:41
Copy link
Contributor Author

renovate bot commented Mar 13, 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-lambda-powertools/[email protected]
npm error node_modules/@aws-lambda-powertools/metrics
npm error   @aws-lambda-powertools/metrics@"2.13.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @aws-lambda-powertools/metrics@"^2.15.0" from @hello.nrfcloud.com/[email protected]
npm error node_modules/@hello.nrfcloud.com/lambda-helpers
npm error   @hello.nrfcloud.com/lambda-helpers@"2.0.90" 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-03-14T23_48_38_111Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-03-14T23_48_38_111Z-debug-0.log

@renovate renovate bot force-pushed the renovate/bifravst-aws-cdk-lambda-helpers-3.x branch 2 times, most recently from 8c205e5 to 2b99e60 Compare March 14, 2025 23:42
@renovate renovate bot changed the title chore(deps): update dependency @bifravst/aws-cdk-lambda-helpers to v3.1.15 chore(deps): update dependency @bifravst/aws-cdk-lambda-helpers to v3.1.19 Mar 14, 2025
@renovate renovate bot force-pushed the renovate/bifravst-aws-cdk-lambda-helpers-3.x branch from 2b99e60 to 013fe6f Compare March 14, 2025 23:45

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
….1.19
@renovate renovate bot force-pushed the renovate/bifravst-aws-cdk-lambda-helpers-3.x branch from 013fe6f to 66b48c5 Compare March 14, 2025 23:48
@renovate renovate bot merged commit 7e772d4 into saga Mar 14, 2025
6 of 8 checks passed
@renovate renovate bot deleted the renovate/bifravst-aws-cdk-lambda-helpers-3.x branch March 14, 2025 23:48
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.

None yet

0 participants