Repository navigation
fix(mastra): install alongside @mastra/otel-exporter 1.5 - #494
Merged
Merged
Conversation
@mastra/otel-exporter 1.5.0 depends on @opentelemetry/api ^1.10.0 and @opentelemetry/sdk-trace-base ^2.12.0, whose peer range stops below api 1.10. Our peer on sdk-trace-base pulled that conflict to the top level, so npm install failed with ERESOLVE (it also failed the #481 release verify). The OpenTelemetry packages the exporter uses are now regular dependencies, as in fi-core; @opentelemetry/core, which nothing imports, is dropped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the npm half of the #481 release failure (run 41264130787). Because the npm job runs the clean-install check on every package before uploading any, this one ERESOLVE kept all 11 pending npm packages off npm.
What broke.
@mastra/otel-exporter1.5.0 (published 2026-10-30) depends on@opentelemetry/api ^1.10.0and@opentelemetry/sdk-trace-base ^2.12.0. sdk-trace-base 2.12.0 has a peer range ofapi >=1.3.0 <1.10.0. On its own, Mastra installs with npm "overriding peer dependency" warnings. Our package declared@opentelemetry/sdk-trace-baseas a peer, which moved that conflict onto the root project, and there npm makes it a hard error:The published 0.2.0 has the same peers, so a fresh
npm install @traceai/mastra @mastra/core @mastra/observability @mastra/otel-exporterfails today.Change.
@opentelemetry/sdk-trace-base,@opentelemetry/exporter-trace-otlp-protoand@opentelemetry/semantic-conventionsare now regular dependencies with the same ranges, the way fi-core declares them. Our exporter imports these itself, so they are implementation details, not something the app supplies.@opentelemetry/coreis dropped from the peers because nothing imports it.@opentelemetry/apistay as peers.pnpm install --frozen-lockfileaccepts it.Checks.
pnpm testin traceai_mastra: 33 passed, offline in the network-denied sandbox.mainplus this change,npm_release.py stageandverifypass for all 11 pending packages: anthropic, bedrock, langchain, llamaindex, mastra, mcp, openai, redis, vercel, vllm and weaviate. Each clean install requires and imports. The mastra install resolved@mastra/otel-exporter1.5.0 andsdk-trace-base2.12.0, andcreateFIMastraExporterandcreateFIObservabilityconstruct and shut down offline.🤖 Generated with Claude Code