Some 0.29.1 packages have dependencies pinned to 1.3.0

[stevoland]

Please answer these questions before submitting a bug report.

What version of OpenTelemetry are you using?

1.3.1

What version of Node are you using?

14.18.2 but using web packages

Please provide the code you used to setup the OpenTelemetry SDK

dependencies: {
    "@opentelemetry/api": "1.1.0",
    "@opentelemetry/context-zone": "1.3.1",
    "@opentelemetry/core": "1.3.1",
    "@opentelemetry/exporter-trace-otlp-http": "0.29.1",
    "@opentelemetry/instrumentation-xml-http-request": "0.29.1",
    "@opentelemetry/resources": "1.3.1",
    "@opentelemetry/sdk-trace-web": "1.3.1",
}

What did you do?

yarn (v1.22.17)

What did you expect to see?

No nested @opentelemetry packages in node_modules

What did you see instead?

@opentelemetry packages at 1.3.0 within @opentelemetry/exporter-trace-otlp-http and @opentelemetry/instrumentation-xml-http-request

Additional context

These packages have their deps pinned to older version which throws exceptions on web:

"dependencies": {
    "@opentelemetry/core": "1.3.0",
    "@opentelemetry/otlp-exporter-base": "0.29.1",
    "@opentelemetry/otlp-transformer": "0.29.1",
    "@opentelemetry/resources": "1.3.0",
    "@opentelemetry/sdk-trace-base": "1.3.0"
  },

#3004

Add any other context about the problem here.

[Flarna]

Is this still an issue with 0.29.2?

[stevoland]

Is this still an issue with 0.29.2?

@Flarna Sorry, hadn't seen 0.29.2. All good, thanks!