SDK can not be installed with @opentelemetry/api@1.0.0

[aabmass]

There is no released version of the SDK compatible with the 1.0.0 api release from last week. The newest API version is not usable. This was fixed in #2276 but needs to be released.

What version of OpenTelemetry are you using?

{
  "name": "npmotel1",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "@opentelemetry/api": "^1.0.0"
  }
}

What version of Node are you using?

~/tmp/npmotel1$ node --version
v12.21.0
~/tmp/npmotel1$ npm --version
7.13.0

Please provide the code you used to setup the OpenTelemetry SDK

n/a

What did you do?

Try to install an SDK package like @opentelemetry/tracing

$ npm install @opentelemetry/tracing@next

What did you expect to see?

Package should install

What did you see instead?

$ npm install @opentelemetry/tracing@next
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: npmotel1@1.0.0
npm ERR! Found: @opentelemetry/api@1.0.0
npm ERR! node_modules/@opentelemetry/api
npm ERR!   @opentelemetry/api@"^1.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @opentelemetry/api@"^0.21.0" from @opentelemetry/tracing@0.21.0
npm ERR! node_modules/@opentelemetry/tracing
npm ERR!   @opentelemetry/tracing@"0.21.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /usr/local/google/home/aaronabbott/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /usr/local/google/home/aaronabbott/.npm/_logs/2021-06-14T17_16_49_782Z-debug.log

[vmarchaud]

cc @dyladan don't know if you wanted to wait for a particular PR to release a SDK version compatible with 1.0 (which should stay in the 0.x version i expect) ?

[dyladan]

yes we will keep it in the 0.x versions for now. I was not waiting for any particular PR

[aabmass]

yes we will keep it in the 0.x versions for now. I was not waiting for any particular PR

Why not use the most recent and now stable 1.0.0 release though? If we want people to use 1.0.0, it should be compatible with some SDK.