Repository navigation
fix(trpc): match @sentry/core to the API's Sentry SDK - #9281
Conversation
Sentry keeps its client under `__SENTRY__[SDK_VERSION]`. #9042 moved the API to @sentry/nextjs 10.75.2 but left packages/trpc on @sentry/core 10.68.0, so every span and captureException from trpc code running in the API has looked in an empty carrier and done nothing since 2026-10-29: the provision job's trace, the cloud-workspace start trace, and the exceptions meter.ts and wake.ts report.
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Dependency version update packages/trpc/package.json |
The declared @sentry/core version changes from 10.68.0 to 10.75.2. |
Estimated code review effort: 1 (Trivial) | ~3 minutes
Change: Bug fix
Possibly related PRs
- ParadevAI/Paradev#9042: Upgrades
@sentry/nextjsinapps/apito the same version. - ParadevAI/Paradev#9267: Adds Sentry tracing in cloud-workspace flows that use
@sentry/core.
Suggested reviewers: harshithmullapudi
Merge Risk: 
96e28
-
The dependency versions are aligned, with no actionable merge-blocking risk identified.
Pre-merge checks: 
-
Check name Status Explanation Title check The title clearly describes the dependency alignment fix and follows the required conventional commit format. Description check The description explains what changed, why it was needed, testing performed, risks, and rollback. It does not use the exact template headings and omits the checklist, but it provides the required core… Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Description check
-
Explanation
The description explains what changed, why it was needed, testing performed, risks, and rollback. It does not use the exact template headings and omits the checklist, but it provides the required core information.
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
No issues found across 2 files
Architecture diagram
sequenceDiagram
participant API as apps/api (@sentry/nextjs 10.75.2)
participant TRPC as packages/trpc (@sentry/core 10.75.2)
participant Carrier as __SENTRY__[SDK_VERSION]
participant Sentry as Sentry Backend
Note over API,TRPC: Runtime telemetry flow after version match
API->>TRPC: Initialize tRPC route (cloud-workspace.provision/start)
TRPC->>Carrier: getSentryCarrier() - lookup by SDK_VERSION 10.75.2
Carrier-->>TRPC: Return shared carrier (now populated)
TRPC->>Sentry: captureException() / startSpan() via shared client
Sentry-->>API: Trace/error reported
Note over API,Sentry: Both packages now share same SDK_VERSION key
 [Medium impact] The PR appears safe to merge. SummaryUpdates
Reviews (1) · Last reviewed commit: "fix(trpc): match @sentry/core to the API..." · Reviewed by Greptile |
|
Preview update published for development build |
🧹 Preview Cleanup CompleteThe following preview resources have been cleaned up:
Thank you for your contribution! 🎉 |
|
Verdict: looks good. The fix is correct. I reproduced the version-keyed carrier miss locally: trpc's Findings:
Checks at Full report: https://app.superset.sh/page/pr-9281-review-trpc-sentry-core-version-match-toivhx Slack post failed: Slack MCP server needs re-authentication |
Summary
@sentry/coreinpackages/trpcfrom 10.68.0 to 10.75.2, the version@sentry/nextjs10.75.2 inapps/apidepends on.Why / Context
Sentry keeps its client under
__SENTRY__[SDK_VERSION](getSentryCarrierin@sentry/core). #9042 moved the API to@sentry/nextjs10.75.2 and leftpackages/trpcon@sentry/core10.68.0. Since then, trpc code running in the API has looked in an empty carrier, so its spans andcaptureExceptioncalls have done nothing:cloud-workspace.provisiontraces stopped. The last one in Sentry is 2026-10-29 23:37 UTC, five minutes before fix(deps): bump next, @sentry/nextjs and vite to resolve Dependabot alerts #9042 merged.cloud-workspace.starttrace from feat(api): trace a cloud workspace from start to host-service answering #9267 records nothing.cloud-workspace/meter.tsandwake.tshave been dropped.Testing
packages/trpc→@sentry/core10.75.2;apps/api's@sentry/nextjs→@sentry/core10.75.2packages/trpc:tsc --noEmit,bun test(841 pass)apps/api:tsc --noEmitRisks / Rollout
Summary by cubic
Bumps
@sentry/coreinpackages/trpcfrom 10.68.0 to 10.75.2 to match the@sentry/nextjsversion inapps/api. Since Sentry stores its client under__SENTRY__[SDK_VERSION], the version mismatch made trpc code running in the API look in an empty carrier, silently dropping spans andcaptureExceptioncalls —cloud-workspace.provisiontraces stopped, the start trace recorded nothing, and exceptions frommeter.tsandwake.tswere lost. Now trpc shares the same Sentry core and telemetry works again. Patch-level upgrade, low risk; verified with type checks and passing tests.Written for commit 96e28dc. Summary will update on new commits.
Summary by CodeRabbit