@sentry/node-core

Important Changes

• cloudflare: Add trace propagation for RPC method calls

  Trace context is now propagated across Cloudflare Workers RPC calls, connecting traces between Workers and Durable Objects.
  This feature is opt-in and requires setting enableRpcTracePropagation: true in your SDK configuration:

  // Worker
  export default Sentry.withSentry(
    env => ({
      dsn: env.SENTRY_DSN,
      enableRpcTracePropagation: true,
    }),
    handler,
  );
  
  // Durable Object
  export const MyDurableObject = Sentry.instrumentDurableObjectWithSentry(
    env => ({
      dsn: env.SENTRY_DSN,
      enableRpcTracePropagation: true,
    }),
    MyDurableObjectBase,
  );

• breaking

  hono: Change setup for @sentry/hono/node (init in external file)

  To improve Node.js instrumentation, the sentry() middleware exported from @sentry/hono/node no longer accepts configuration options.
  Instead, you must configure the SDK by calling Sentry.init() in a dedicated instrumentation file that runs before your application code (read more in the Hono SDK readme:

  // instrument.mjs (or instrument.ts)
  import * as Sentry from '@sentry/hono/node';
  
  Sentry.init({
    dsn: '__DSN__',
    tracesSampleRate: 1.0,
  });

• nitro: Add @sentry/nitro SDK

  A new @sentry/nitro package provides first-class Sentry support for Nitro applications, with HTTP handler and error instrumentation, middleware tracing, request isolation, and build-time source map uploading via withSentryConfig.
  Read more in the Nitro SDK docs and the Nitro SDK readme.

Other Changes

• astro: Drop prerendered http.server filter via ignoreSpans

• aws-serverless: Validate extension tunnel DSN against SENTRY_DSN

• browser: Add ingest_settings to span v2 envelope payload

• browser: Add support for streamed spans in httpContextIntegration

• core: Backfill otel attributes on streamed spans

• core: Clear up integrations on dispose

• core: Instrument langgraph createReactAgent

• core: Support attribute matching in ignoreSpans

• feedback: Allow error messages to be customized

• hono: Support middleware spans defined in app groups

• nextjs: Filter unwanted segments when span streaming is enabled

• nextjs: Migrate edge event processors to span-first APIs

• nextjs: Migrate server event processors to span-first APIs

• nextjs: Set global attribute for turbopack usage

• nitro: Nitro SDK

• react-router: Clean up bogus * http.route attribute on segment spans

• react-router: Drop low-quality transactions via ignoreSpans

• sveltekit: Support span streaming in svelteKitSpansEnhancement integration

• tanstackstart-react: Add dynamic tunnel route helper and generator

• Update prisma v7 spans descriptions

• core: Avoid parse-time SyntaxError on Safari <16.4 in postgresjs

• core: Ensure isSentryRequest handles subdomains properly

• core: Ensure ip address headers are stripped when lower case

• core: Filter more cookie names for PII

• core: Use symbol for normalization checks

• hono: Distinguish .use() middleware in sub-apps from .all() handlers

• nextjs: Ensure we do not match tunnel endpoints too broadly

• opentelemetry: Add conditional browser export to avoid node deps

• replay: Avoid main-thread blocking in WorkerHandler under event bursts

• replay: Ensure maskAttributes works with maskAllText=false

• supabase: Consider sendDefaultPii for supabase integration

Internal Changes

• e2e/tanstackstart-react: Pin @tanstack/start-plugin-core to unblock CI