OpenTelemetry JavaScript 3.0 Readiness

Use this checklist to assess applications, libraries, and custom instrumentation before adopting OpenTelemetry JS 3.0. The upstream announcement and main-branch migration guide describe the 3.x migration; a scheduled date or development package is not proof of a stable release. Verify the official release tag, npm latest dist-tag, and target package versions before upgrading.

For applications remaining on JS 2.11, test context attach/disposal on the supported Node runtime and per-call flush timeouts. A stable 2.x update does not establish readiness for 3.x.

Readiness checklist

• Confirm the stable 3.x release and its release notes. Do not treat a development/canary version as a production release.
• Set the application and CI Node.js floor to 22.15.0 or later. The upstream announcement exempts @opentelemetry/api and @opentelemetry/semantic-conventions from this SDK runtime floor; verify the requirements of each installed package.
• Remove packages scheduled for removal: @opentelemetry/propagator-jaeger, @opentelemetry/exporter-jaeger, @opentelemetry/shim-opentracing, @opentelemetry/shim-opencensus, @opentelemetry/api-logs, @opentelemetry/instrumentation-restify, @opentelemetry/sdk-trace-base, @opentelemetry/sdk-trace-node, and @opentelemetry/sdk-trace-web. Check the final stable migration guide because removals may shift before release.
• Migrate Jaeger propagation to W3C Trace Context across communicating services; if a staged migration requires the legacy propagator, confirm the migration guide's compatibility constraints before retaining it.
• Migrate tracing SDK imports to @opentelemetry/sdk-trace. Replace BasicTracerProvider with TracerProvider; register the provider, context manager, and propagator explicitly where prior Node/Web provider .register() behavior was used.
• Review span processor construction for the new options-object form, including { exporter }, and move environment/file-driven configuration to sdk-node if needed; the consolidated trace SDK no longer reads the listed trace/provider and span-processor environment variables.
• Search source and configuration for removed APIs/options too, including HttpInstrumentationConfig.serverName and singular NodeSDK processor/reader options; follow the final migration guide for replacements.
• Review custom instrumentation separately. Code using only the stable @opentelemetry/api is expected to remain compatible; instrumentation authors and packages that depend on SDK classes, removed utilities, or @opentelemetry/instrumentation internals require explicit source review and tests. Do not infer compatibility from an API-only guarantee.
• Run unit/integration tests on the minimum supported Node version and verify context propagation, span export, instrumentation patching, and graceful shutdown.

Upstream references

• OpenTelemetry JS 3.x announcement
• OpenTelemetry JS 3.x migration guide
• OpenTelemetry JS releases
• npm stable package metadata