Skip to content

fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.60.0 - autoclosed #407

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 24, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@opentelemetry/auto-instrumentations-node (source) ^0.44.0 -> ^0.60.0 age adoption passing confidence

Release Notes

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

v0.60.0

Compare Source

v0.59.0

Compare Source

v0.58.1

Compare Source

v0.58.0

Compare Source

v0.57.1

Compare Source

v0.57.0

Compare Source

v0.56.1

Compare Source

v0.56.0

Compare Source

v0.55.3

Compare Source

v0.55.2

Compare Source

v0.55.1

Compare Source

v0.55.0

Compare Source

v0.54.0

Compare Source

v0.53.0

Compare Source

v0.52.1

Compare Source

v0.52.0

Compare Source

v0.51.0

Compare Source

v0.50.2

Compare Source

v0.50.1

Compare Source

v0.50.0

Compare Source

v0.49.2

Compare Source

v0.49.1

Compare Source

v0.49.0

Compare Source

v0.48.0

Compare Source

v0.47.1

Compare Source

v0.47.0

Compare Source

v0.46.1

Compare Source

v0.46.0

Compare Source

v0.45.0

Compare Source


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.

@renovate renovate bot added the renovate label Dec 24, 2024
@renovate renovate bot force-pushed the renovate/opentelemetry-js-contrib-monorepo branch from 7e4f2c7 to e07ae1e Compare January 28, 2025 14:35
@renovate renovate bot changed the title fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.55.0 fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.56.0 Jan 28, 2025
@renovate renovate bot changed the title fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.56.0 fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.57.0 Mar 18, 2025
@renovate renovate bot force-pushed the renovate/opentelemetry-js-contrib-monorepo branch from e07ae1e to a079115 Compare March 18, 2025 19:13
@renovate renovate bot force-pushed the renovate/opentelemetry-js-contrib-monorepo branch from a079115 to 14db525 Compare April 17, 2025 12:30
@renovate renovate bot changed the title fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.57.0 fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.58.0 Apr 17, 2025
Copy link
Contributor Author

renovate bot commented Apr 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: openfeature@0.16.0
npm error Found: @opentelemetry/core@1.30.1
npm error node_modules/@opentelemetry/core
npm error   @opentelemetry/core@"^1.23.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @opentelemetry/core@"^2.0.0" from @opentelemetry/auto-instrumentations-node@0.60.0
npm error node_modules/@opentelemetry/auto-instrumentations-node
npm error   @opentelemetry/auto-instrumentations-node@"^0.60.0" 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-06-02T18_16_31_499Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-06-02T18_16_31_499Z-debug-0.log

@renovate renovate bot force-pushed the renovate/opentelemetry-js-contrib-monorepo branch from 14db525 to 4b2c877 Compare May 15, 2025 21:58
@renovate renovate bot changed the title fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.58.0 fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.59.0 May 15, 2025
@renovate renovate bot force-pushed the renovate/opentelemetry-js-contrib-monorepo branch from 4b2c877 to 3bc1a62 Compare June 2, 2025 18:16
@renovate renovate bot changed the title fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.59.0 fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.60.0 Jun 2, 2025
@renovate renovate bot changed the title fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.60.0 fix(deps): update dependency @opentelemetry/auto-instrumentations-node to ^0.60.0 - autoclosed Jul 4, 2025
@renovate renovate bot closed this Jul 4, 2025
@renovate renovate bot deleted the renovate/opentelemetry-js-contrib-monorepo branch July 4, 2025 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants