Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 11, 2025

This PR contains the following updates:

Package Change Age Confidence
@opentelemetry/auto-instrumentations-node (source) ^0.40.3 -> ^0.62.0 age confidence

Release Notes

open-telemetry/opentelemetry-js-contrib (@​opentelemetry/auto-instrumentations-node)

v0.62.1

Compare Source

Dependencies

v0.62.0

Compare Source

Features
Dependencies

v0.61.0

Compare Source

⚠ BREAKING CHANGES
  • instrumentation-redis: consolidate redis v2,3 and redis v4 instrumentation to one package (#​2915)
Features
  • instrumentation-redis: consolidate redis v2,3 and redis v4 instrumentation to one package (#​2915) (5988c79)
Dependencies

v0.60.1

Compare Source

Dependencies

v0.60.0

Compare Source

Features
Dependencies

v0.59.0

Compare Source

Features
Dependencies

v0.58.1

Compare Source

Dependencies

v0.58.0

Compare Source

Features
Dependencies

v0.57.1

Compare Source

Dependencies

v0.57.0

Compare Source

⚠ BREAKING CHANGES
  • chore!: Update to 2.x and 0.200.x @​opentelemetry/* packages from opentelemetry-js.git per 2.x upgrade guide
    • The minimum supported Node.js has been raised to ^18.19.0 || >=20.6.0. This means that support for Node.js 14 and 16 has been dropped.
    • The minimum supported TypeScript version has been raised to 5.0.4.
    • The compilation target for transpiled TypeScript has been raised to ES2022 (from ES2017).
Bug Fixes
Miscellaneous Chores
Dependencies

v0.56.1

Compare Source

Bug Fixes
Dependencies

v0.56.0

Compare Source

⚠ BREAKING CHANGES
Features
Dependencies

v0.55.3

Compare Source

Bug Fixes
  • auto-instrumentations-node: correct typo (#​2666) (4cf7e6f)
  • auto-instrumentations-node: make SIGTERM shutdown test more reliable (#​2667) (94414a1)
Dependencies

v0.55.2

Compare Source

Dependencies

v0.55.1

Compare Source

Dependencies

v0.55.0

Compare Source

Features
Dependencies

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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.

Copy link
Contributor Author

renovate bot commented Aug 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: [email protected]
npm error Found: @opentelemetry/[email protected]
npm error node_modules/@opentelemetry/core
npm error   @opentelemetry/core@"1.19.0" from [email protected]
npm error   subgraphs/posts
npm error     [email protected]
npm error     node_modules/ol-subgraph-posts
npm error       workspace subgraphs/posts from the root project
npm error
npm error Could not resolve dependency:
npm error peer @opentelemetry/core@"^2.0.0" from @opentelemetry/[email protected]
npm error node_modules/@opentelemetry/auto-instrumentations-node
npm error   @opentelemetry/auto-instrumentations-node@"^0.62.0" from [email protected]
npm error   subgraphs/posts
npm error     [email protected]
npm error     node_modules/ol-subgraph-posts
npm error       workspace subgraphs/posts 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-09-01T09_28_27_216Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-09-01T09_28_27_216Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants