fix(trpc): match @sentry/core to the API's Sentry SDK

Merged
SA
6d ago
+9-17

Summary

  • Bump @sentry/core in packages/trpc from 10.68.0 to 10.75.2, the version @sentry/nextjs 10.75.2 in apps/api depends on.

Why / Context

Sentry keeps its client under __SENTRY__[SDK_VERSION] (getSentryCarrier in @sentry/core). #9042 moved the API to @sentry/nextjs 10.75.2 and left packages/trpc on @sentry/core 10.68.0. Since then, trpc code running in the API has looked in an empty carrier, so its spans and captureException calls have done nothing:

  • The cloud-workspace.provision traces stopped. The last one in Sentry is 2026-10-29 23:37 UTC, five minutes before #9042 merged.
  • The cloud-workspace.start trace from #9267 records nothing.
  • Exceptions reported from cloud-workspace/meter.ts and wake.ts have been dropped.

Testing

  • Resolved versions: packages/trpc → @sentry/core 10.75.2; apps/api's @sentry/nextjs → @sentry/core 10.75.2
  • packages/trpc: tsc --noEmit, bun test (841 pass)
  • apps/api: tsc --noEmit
  • After deploy: create one cloud workspace and check that its start and provision transactions appear in Sentry as one trace

Risks / Rollout

  • Risk: low. Patch-level upgrades within the Sentry 10.x line that the API already runs.
  • Rollback: revert the commit.

Summary by cubic

Bumps @sentry/core in packages/trpc from 10.68.0 to 10.75.2 to match the @sentry/nextjs version in apps/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 and captureException calls — cloud-workspace.provision traces stopped, the start trace recorded nothing, and exceptions from meter.ts and wake.ts were lost. Now trpc shares the same Sentry core and telemetry works again. Patch-level upgrade, low risk; verified with type checks and passing tests.

Summary by CodeRabbit

  • Chores
    • Updated an underlying component. No user-facing changes are noted.