feat(renovate): widen @opentelemetry/* peer-dep ranges#45
Merged
Conversation
Libraries declaring @opentelemetry/api as a peer dep must let the consumer control the installed version. Narrowing the peer range risks a second copy of @opentelemetry/api resolving alongside the consumer's: provider.register() hits one module's singleton while trace.getTracer() reads the other, producing silent no-op spans with no error surface. rangeStrategy=widen keeps the existing range satisfied while also admitting the newer version, so Renovate bumps the API package in consumers without forcing lib churn. Scoped to @opentelemetry/** in peerDependencies only; regular deps still follow the default bump strategy.
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.
Summary
@opentelemetry/*packagespeerDependenciesonly; regular deps still bump as beforeWhy
Preparing for JRL-11 (OTel instrumentation in
xstate-nats+xstate-duckdb). Those libs will declare@opentelemetry/apias a peer dep.@opentelemetry/apiexposes a global singleton —provider.register()andtrace.getTracer()must touch the same module copy, else spans silently become no-ops. A narrow peer range in a library can force a second copy of the api package to resolve alongside the consumer's, breaking OTel end-to-end with no error surface.rangeStrategy: "widen"keeps the existing peer range satisfied while also admitting the new upper bound, so Renovate can bump the api package in consumers without churning every library release.Linked: JRL-11
Test plan
@opentelemetry/apias peerDep behaves aswiden(e.g.^1.9.0→^1.9.0 || ^1.10.0) rather thanbump(^1.9.0→^1.10.0)