feat(deps): bump @opentelemetry/instrumentation-http from 0.57.2 to 0.203.0#17004
Conversation
Bumps [@opentelemetry/instrumentation-http](https://github.com/open-telemetry/opentelemetry-js) from 0.57.2 to 0.203.0. - [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-js@experimental/v0.57.2...experimental/v0.203.0) --- updated-dependencies: - dependency-name: "@opentelemetry/instrumentation-http" dependency-version: 0.203.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Bug: OpenTelemetry Dependency Conflict After Upgrade
The upgrade of @opentelemetry/instrumentation-http to 0.203.0 introduces a dependency conflict. This new version requires @opentelemetry/core@2.0.1 and @opentelemetry/instrumentation@0.203.0, but the package.json still specifies older, incompatible versions (@opentelemetry/core@^1.30.1 and @opentelemetry/instrumentation@^0.57.2). This mismatch will cause multiple major versions of OpenTelemetry packages to be bundled, potentially leading to runtime errors and API incompatibilities.
packages/node/package.json#L79-L80
sentry-javascript/packages/node/package.json
Lines 79 to 80 in d9d2975
dev-packages/node-core-integration-tests/package.json#L32-L33
Was this report helpful? Give feedback by reacting with 👍 or 👎
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps @opentelemetry/instrumentation-http from 0.57.2 to 0.203.0.
Release notes
Sourced from
@opentelemetry/instrumentation-http's releases.... (truncated)
Commits
93187f0chore: prepare next release (#5788)ca6ae61chore: sync package-lock.json (#5782)407c98arefactor(otlp-exporter-base): remove pre-Node.js 14 compatibility code (#5787)27d5171ci: add write permissions for secuity events (#5786)7a32f86Add minimum token permissions for all github workflow files (#5771)5c4057bfix(docs): fix minimum ECMAScript language support in Readme to ES2022 (#5774)553db87refactor(sdk-node): fix eslint warning (#5400)74d434eci: remove unused label-releases workflow (#5772)a59d707Standardize contributing section (#5767)491ed96feat(sdk-logs)!: Removed deprecatedLoggerProvider#addLogRecordProcessor()...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)