Update opentelemetry-js monorepo#1687
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/opentelemetry-js-monorepo
branch
9 times, most recently
from
caab0ae to
d15ecf3
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-js-monorepo
branch
11 times, most recently
from
941c2cb to
22fb61c
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-js-monorepo
branch
9 times, most recently
from
48ca38e to
d2da4ea
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-js-monorepo
branch
from
d2da4ea to
aa165ec
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-js-monorepo
branch
22 times, most recently
from
066103f to
4ef2355
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-js-monorepo
branch
5 times, most recently
from
7f2d126 to
e5436e2
Compare
Renovate bumped the exporter from 0.57.0 to 0.218.0, which crosses the OpenTelemetry experimental-package fork at 0.200.0 — from there on the exporter requires OTel SDK v2.x (sdk-trace-base@2.x, which adds a required `instrumentationScope` field on ReadableSpan). Our root tree is still on sdk-trace-base@1.30.1 because @sentry/node@8.55.2 pins @opentelemetry/core: ^1.30.1, so tsc saw two incompatible SpanExporter trees at src/instrumentation.ts:70. Pin the exporter to 0.57.2 (latest v1.x-compatible patch, bug fixes over 0.57.0). Keep the safe @opentelemetry/api 1.9.0 → 1.9.1 bump. Add Renovate package rules to stop future cross-major jumps until @sentry/node is upgraded to 10.x, which targets OTel v2.x. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.9.0→1.9.10.57.0→0.218.0Release Notes
open-telemetry/opentelemetry-js (@opentelemetry/api)
v1.9.1Compare Source
🐛 (Bug Fix)
#3562 @scheler
🏠 (Internal)
Configuration
📅 Schedule: (UTC)
* 7-16 * * 1,2,3,4)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.