chore(deps): bump @sentry/react from 10.71.0 to 10.73.0

[brandhaug]

Dependency Updates

Package	From	To	Type
@sentry/react	10.71.0	10.73.0	minor

Release Notes

@sentry/react (10.71.0 → 10.73.0) — 2 releases

10.73.0

Important Changes

• feat(v10/nextjs): Add @sentry/nextjs/config entry point (#23766)

  withSentryConfig is now available from @sentry/nextjs/config, the path it moves to in v11. Importing it from @sentry/nextjs still works on v10 but logs a warning once, so you can change your next.config file today and upgrade to v11 without touching it again.

  // next.config.mjs
  - import { withSentryConfig } from '@sentry/nextjs';
  + import { withSentryConfig } from '@sentry/nextjs/config';

Other Changes

• feat(v10/node): Deprecate shouldHandleError on setupExpressErrorHandler and setupFasitfyErrorHandler (#23734)
• fix(v10/cloudflare): Instrument Durable Object handlers installed as read-only properties (#23769)

Internal Changes

• test(v10/nextjs): Drop nextjs-16-cf-workers canary variant (#23775)

Bundle size 📦

Path	Size
@sentry/browser	27.1 KB
@sentry/browser - with treeshaking flags	25.58 KB
@sentry/browser (incl. Tracing)	45.54 KB
@sentry/browser (incl. Tracing + Span Streaming)	47.28 KB
@sentry/browser (incl. Tracing, Profiling)	50.17 KB
@sentry/browser (incl. Tracing, Replay)	83.87 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags

…full notes

10.72.0

Important Changes

• AI integrations no longer report errors that propagate to the caller (#23638, #23639, #23640)

  Across all AI integrations (OpenAI, Anthropic, Google GenAI, LangChain, and LangGraph), the SDK no longer sends an event to Sentry for errors that the AI framework propagates to your code. Previously the instrumentation reported these as unhandled (handled: false) before your own error handling ran, so an error your code caught still showed up in Sentry as an unhandled crash. The span is still marked as errored and the error still propagates, so reporting is left to your application: if your code does not handle the error, it reaches Sentry's global error handlers and is captured as unhandled, just like any other uncaught error. Errors that a provider surfaces as data on an otherwise successful response (such as Anthropic error-shaped responses or Google GenAI blocked content) are still captured, since your code never sees them propagate.

• feat(v10/cloudflare): Add rpcTracePropagationBindings (#23737, #23738)

  The new rpcTracePropagationBindings option names the env bindings that outgoing RPC calls propagate trace context to. Strings match a binding name exactly, regular expressions match by pattern, and the default empty array propagates to nothing. RPC has no headers to carry trace context, so the SDK appends it as a trailing argument that only a Sentry-instrumented receiver removes again. List only the bindings whose receiver you know runs Sentry. Setting the option takes precedence over enableRpcTracePropagation, which is now deprecated. When you build with the Sentry Cloudflare Vite plugin, the bindings that resolve to t

…full notes

---

This PR was auto-generated by catalog-update-action.

[github-actions]

Preview stage pr-210

Destroyed: the D1 database, queues, and Workers for this stage are gone.