fix: use api 1.1 in SDKs (#2759)

Use API 1.1 in SDKs to avoid that SDKs register a TracerProvider,... using an older API then other OTel components. This avoids the version check in API rejecting the use of API 1.1 but a peer may still use 1.0.x.
open-telemetry · Feb 5, 2022 · e9e4567 · e9e4567
1 parent ee2342b
commit e9e4567
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/packages/opentelemetry-sdk-trace-base/package.json b/packages/opentelemetry-sdk-trace-base/package.json
@@ -83,7 +83,7 @@
     "webpack": "4.46.0"
   },
   "peerDependencies": {
-    "@opentelemetry/api": ">=1.0.0 <1.2.0"
+    "@opentelemetry/api": ">=1.1.0 <1.2.0"
   },
   "dependencies": {
     "@opentelemetry/core": "1.0.1",

diff --git a/packages/opentelemetry-sdk-trace-node/package.json b/packages/opentelemetry-sdk-trace-node/package.json
@@ -59,7 +59,7 @@
     "typescript": "4.4.4"
   },
   "peerDependencies": {
-    "@opentelemetry/api": ">=1.0.0 <1.2.0"
+    "@opentelemetry/api": ">=1.1.0 <1.2.0"
   },
   "dependencies": {
     "@opentelemetry/context-async-hooks": "1.0.1",

diff --git a/packages/opentelemetry-sdk-trace-web/package.json b/packages/opentelemetry-sdk-trace-web/package.json
@@ -86,7 +86,7 @@
     "webpack-merge": "5.8.0"
   },
   "peerDependencies": {
-    "@opentelemetry/api": ">=1.0.0 <1.2.0"
+    "@opentelemetry/api": ">=1.1.0 <1.2.0"
   },
   "dependencies": {
     "@opentelemetry/core": "1.0.1",