Use version ranges for peer deps (#101)

* Use version ranges for peer deps

* changeset

* `&&` is not a valid token in the semver requirement

* update peer deps version ranges

---------

Co-authored-by: Darpan Kakadia <[email protected]>

Author: dvoytenko

.changeset/ten-ties-raise.md

@@ -0,0 +1,5 @@
+---
+"@vercel/otel": minor
+---
+
+Expand a set of OTEL versions for peer dependencies

packages/otel/package.json

@@ -91,12 +91,12 @@
     "vitest": "0.33.0"
   },
   "peerDependencies": {
-    "@opentelemetry/api": "^1.7.0",
-    "@opentelemetry/api-logs": ">=0.46.0 && <1.0.0",
-    "@opentelemetry/instrumentation": ">=0.46.0 && <1.0.0",
-    "@opentelemetry/resources": "^1.19.0",
-    "@opentelemetry/sdk-logs": ">=0.46.0 && <1.0.0",
-    "@opentelemetry/sdk-metrics": "^1.19.0",
-    "@opentelemetry/sdk-trace-base": "^1.19.0"
+    "@opentelemetry/api": ">=1.7.0 <2.0.0",
+    "@opentelemetry/api-logs": ">=0.46.0 <0.200.0",
+    "@opentelemetry/instrumentation": ">=0.46.0 <0.200.0",
+    "@opentelemetry/resources": ">=1.19.0 <2.0.0",
+    "@opentelemetry/sdk-logs": ">=0.46.0 <0.200.0",
+    "@opentelemetry/sdk-metrics": ">=1.19.0 <2.0.0",
+    "@opentelemetry/sdk-trace-base": ">=1.19.0 <2.0.0"
   }
 }