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 @opentelemetry/api to v1.9.0 #6928

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 20, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@opentelemetry/api (source) 1.8.0 -> 1.9.0 age adoption passing confidence

Release Notes

open-telemetry/opentelemetry-js (@​opentelemetry/api)

v1.9.0

Compare Source

🚀 (Enhancement)
  • feat(instrumentation-grpc): set net.peer.name and net.peer.port on client spans #​3430
  • feat(exporter-trace-otlp-proto): Add protobuf otlp trace exporter support for browser #​3208 @​pkanal
🐛 (Bug Fix)
  • fix(sdk-metrics): use default Resource to comply with semantic conventions #​3411 @​pichlermarc
    • Metrics exported by the SDK now contain the following resource attributes by default:
      • service.name
      • telemetry.sdk.name
      • telemetry.sdk.language
      • telemetry.sdk.version
  • fix(sdk-metrics): use Date.now() for instrument recording timestamps #​3514 @​MisterSquishy
  • fix(sdk-trace): make spans resilient to clock drift #​3434 @​dyladan
  • fix(selenium-tests): updated webpack version for selenium test issue #​3456 @​SaumyaBhushan
  • fix(sdk-metrics): collect metrics when periodic exporting metric reader flushes #​3517 @​legendecas
  • fix(sdk-metrics): fix duplicated registration of metrics for collectors #​3488 @​legendecas
  • fix(core): fix precision loss in numberToHrtime #​3480 @​legendecas
🏠 (Internal)

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Nov 20, 2024
@renovate renovate bot requested a review from a team as a code owner November 20, 2024 17:07
@renovate renovate bot enabled auto-merge (squash) November 20, 2024 17:07
Copy link
Contributor Author

renovate bot commented Nov 20, 2024

⚠️ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @netlify/build@29.56.1
npm ERR! Found: @opentelemetry/api@1.9.0
npm ERR! node_modules/@opentelemetry/api
npm ERR!   @opentelemetry/api@"1.9.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @opentelemetry/api@"~1.8.0" from @netlify/build@29.56.1
npm ERR! node_modules/@netlify/build
npm ERR!   @netlify/build@"29.56.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @opentelemetry/api@1.8.0
npm ERR! node_modules/@opentelemetry/api
npm ERR!   peer @opentelemetry/api@"~1.8.0" from @netlify/build@29.56.1
npm ERR!   node_modules/@netlify/build
npm ERR!     @netlify/build@"29.56.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-20T17_07_16_282Z-debug-0.log

@sarahetter
Copy link
Contributor

Conflicting peer dependency with @netlify-build - don't retry until that's updated :)

@sarahetter sarahetter closed this Nov 20, 2024
auto-merge was automatically disabled November 20, 2024 19:15

Pull request was closed

Copy link
Contributor Author

renovate bot commented Nov 20, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (1.9.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/opentelemetry-js-monorepo branch November 20, 2024 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant