@opentelemetry/sdk-node breaking changes
Every breaking API change we have recorded in @opentelemetry/sdk-node on npm: 11 breaking changes in 1 version. Below are its newest version, removals and renames first, each with its source.
Newest change October 20, 2026
On this page
0.300.0
- Removed
api
api was removed in @opentelemetry/sdk-node 0.300.0 npmjs.com - Removed
contextBase
contextBase was removed in @opentelemetry/sdk-node 0.300.0 npmjs.com - Removed
core
core was removed in @opentelemetry/sdk-node 0.300.0 npmjs.com - Removed
logs
logs was removed in @opentelemetry/sdk-node 0.300.0 npmjs.com - Removed
metrics
metrics was removed in @opentelemetry/sdk-node 0.300.0 npmjs.com - Removed
node
node was removed in @opentelemetry/sdk-node 0.300.0 npmjs.com - Removed
NodeSDKConfiguration.logRecordProcessor
Use logRecordProcessors instead. npmjs.com - Removed
NodeSDKConfiguration.metricReader
Use metricReaders instead. npmjs.com - Removed
NodeSDKConfiguration.spanProcessor
Use spanProcessors instead. npmjs.com - Removed
resources
resources was removed in @opentelemetry/sdk-node 0.300.0 npmjs.com
And 1 more in this version.
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.
Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp