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

fix(deps): update dependency @aws-lambda-powertools/metrics to v2.16.0 #528

Merged
merged 1 commit into from
Mar 17, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 11, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@aws-lambda-powertools/metrics (source) 2.13.1 -> 2.16.0 age adoption passing confidence

Release Notes

aws-powertools/powertools-lambda-typescript (@​aws-lambda-powertools/metrics)

v2.16.0

Compare Source

Bug Fixes
Features

v2.15.0

Compare Source

Bug Fixes
Features

v2.14.0

Compare Source

Bug Fixes
  • logger: prevent overwriting standard keys (#​3553) (f0bdf3c)
  • parser: parse sqs record body field as JSON and S3Schema in S3SqsEventNoificationRecordSchema (#​3529) (bcd4b9f)
Features

2.13.1 (2025-01-28)

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 Feb 11, 2025
@renovate renovate bot enabled auto-merge (squash) February 11, 2025 13:10
Copy link
Contributor Author

renovate bot commented Feb 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: @middy/[email protected]
npm error node_modules/@middy/core
npm error   @middy/core@"6.0.0" from the root project
npm error   peerOptional @middy/core@"4.x || 5.x || 6.x" from @aws-lambda-powertools/[email protected]
npm error   node_modules/@aws-lambda-powertools/metrics
npm error     @aws-lambda-powertools/metrics@"2.16.0" from the root project
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 Could not resolve dependency:
npm error peer @middy/core@"^6.1.4" 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-17T01_31_55_125Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-03-17T01_31_55_125Z-debug-0.log

@renovate renovate bot force-pushed the renovate/aws-lambda-powertools-typescript-monorepo branch 17 times, most recently from 5bc927d to 1996557 Compare February 17, 2025 21:36
@renovate renovate bot force-pushed the renovate/aws-lambda-powertools-typescript-monorepo branch 9 times, most recently from 3460050 to 118e5ca Compare February 23, 2025 05:27
@renovate renovate bot changed the title fix(deps): update dependency @aws-lambda-powertools/metrics to v2.15.0 fix(deps): update dependency @aws-lambda-powertools/metrics to v2.16.0 Mar 7, 2025
@renovate renovate bot force-pushed the renovate/aws-lambda-powertools-typescript-monorepo branch 13 times, most recently from f53f084 to e900245 Compare March 13, 2025 18:48
@renovate renovate bot force-pushed the renovate/aws-lambda-powertools-typescript-monorepo branch 12 times, most recently from fa29fc0 to 339a84d Compare March 16, 2025 21:15
@renovate renovate bot force-pushed the renovate/aws-lambda-powertools-typescript-monorepo branch from 339a84d to e287059 Compare March 17, 2025 01:32
@renovate renovate bot merged commit 4ee4d69 into saga Mar 17, 2025
7 of 9 checks passed
@renovate renovate bot deleted the renovate/aws-lambda-powertools-typescript-monorepo branch March 17, 2025 01:32
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