set an explicit version range for the @opentelemetry/api #4318
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.
What does this PR do?
sets an explicit version range for the @opentelemetry/api
Motivation
#3654
TLDR:
"Short version: an SDK implementation should expect that minor versions of the API may include new methods. Minor version stability is guaranteed for users but not implementers. The OpenTelemetry authors recommend the following: dd-trace should define not only a minimum API level but also a maximum"
the version maximum is set to <1.9.0 which is expected to break us:
open-telemetry/opentelemetry-js#4677 (comment)
Additional Notes
Should we take the approach of listing the supported version range as a "peerDependencies"? Although it will ensure that users install the supported versions of the @opentelemetry/api it will also force users not using the @opentelemetry/api to have to install it.