Summary
@opentelemetry/api@1.9.1 was released on Mar 25 and introduced export { Foo, type Bar } syntax (inline type modifiers) in its .d.ts files, which requires TypeScript 4.5+- The
generic-ts3.8 E2E test runs with skipLibCheck: false and TypeScript 3.8, so it tries to parse OTel's types and fails - This pins
@opentelemetry/api to 1.9.0 in the ts3.8 test app via pnpm.overrides - We can't pin repo-wide in published packages because OTel uses a global singleton pattern — version mismatches with
@opentelemetry/sdk-trace-base cause the tracer to become a no-op - Our published
.d.ts files are unaffected — only OTel's own types use the incompatible syntax
Test plan
🤖 Generated with Claude Code
Note
The pull request "fix(e2e): Pin @opentelemetry/api to 1.9.0 in ts3.8 test app" was created by @logaretm but did not reference an issue. Therefore this issue was created for better visibility in external tools like Linear.
Summary
@opentelemetry/api@1.9.1was released on Mar 25 and introducedexport { Foo, type Bar }syntax (inline type modifiers) in its.d.tsfiles, which requires TypeScript 4.5+generic-ts3.8E2E test runs withskipLibCheck: falseand TypeScript 3.8, so it tries to parse OTel's types and fails@opentelemetry/apito1.9.0in the ts3.8 test app viapnpm.overrides@opentelemetry/sdk-trace-basecause the tracer to become a no-op.d.tsfiles are unaffected — only OTel's own types use the incompatible syntaxTest plan
yarn test:run generic-ts3.8passes with the pinE2E generic-ts3.8 Testshould go green🤖 Generated with Claude Code