v10.43.0

Compare Source

Important Changes

• feat(nextjs): Add Turbopack support for React component name annotation (#​19604)

  We added experimental support for React component name annotation in Turbopack builds. When enabled, JSX elements are annotated with data-sentry-component, data-sentry-element, and data-sentry-source-file attributes at build time. This enables searching Replays by component name, seeing component names in breadcrumbs, and performance monitoring — previously only available with webpack builds.

  This feature requires Next.js 16+ and is currently behind an experimental flag:

  // next.config.ts
  import { withSentryConfig } from '@​sentry/nextjs';
  
  export default withSentryConfig(nextConfig, {
    _experimental: {
      turbopackReactComponentAnnotation: {
        enabled: true,
        ignoredComponents: ['Header', 'Footer'], // optional
      },
    },
  });

• feat(hono): Instrument middlewares app.use() (#​19611)

  Hono middleware registered via app.use() is now automatically instrumented, creating spans for each middleware invocation.

Other Changes

• feat(node-core,node): Add tracePropagation option to http and fetch integrations (#​19712)
• feat(hono): Use parametrized names for errors (#​19577)
• fix(browser): Fix missing traces for user feedback (#​19660)
• fix(cloudflare): Use correct Proxy receiver in instrumentDurableObjectStorage (#​19662)
• fix(core): Standardize Vercel AI span descriptions to align with GenAI semantic conventions (#​19624)
• fix(deps): Bump hono to 4.12.5 to fix multiple vulnerabilities (#​19653)
• fix(deps): Bump svgo to 4.0.1 to fix DoS via entity expansion (#​19651)
• fix(deps): Bump tar to 7.5.10 to fix hardlink path traversal (#​19650)
• fix(nextjs): Align Turbopack module metadata injection with webpack behavior (#​19645)
• fix(node): Prevent duplicate LangChain spans from double module patching (#​19684)
• fix(node-core,vercel-edge): Use HEROKU_BUILD_COMMIT env var for default release (#​19617)
• fix(sveltekit): Fix file system race condition in source map cleaning (#​19714)
• fix(tanstackstart-react): Add workerd and worker export conditions (#​19461)
• fix(vercel-ai): Prevent tool call span map memory leak (#​19328)
• feat(deps): Bump @​sentry/rollup-plugin from 5.1.0 to 5.1.1 (#​19658)

Work in this release was contributed by @​dmmulroy, @​lithdew, and @​smorimoto. Thank you for your contributions!

v10.42.0

Compare Source

• feat(consola): Enhance Consola integration to extract first-param object as searchable attributes (#​19534)
• fix(astro): Do not inject withSentry into Cloudflare Pages (#​19558)
• fix(core): Do not remove promiseBuffer entirely (#​19592)
• fix(deps): Bump fast-xml-parser to 4.5.4 for CVE-2026-25896 (#​19588)
• fix(react-router): Set correct transaction name when navigating with object argument (#​19590)
• ref(nuxt): Use addVitePlugin instead of deprecated vite:extendConfig (#​19464)

v10.41.0

Compare Source

Important Changes

• feat(core,cloudflare,deno): Add instrumentPostgresJsSql instrumentation (#​19566)

  Added a new instrumentation helper for the postgres (postgres.js) library, designed for SDKs that are not based on OpenTelemetry (e.g. Cloudflare, Deno). This wraps a postgres.js sql tagged template instance so that all queries automatically create Sentry spans.

  import postgres from 'postgres';
  import * as Sentry from '@​sentry/cloudflare'; // or '@​sentry/deno'
  
  export default Sentry.withSentry(env => ({ dsn: '__DSN__' }), {
    async fetch(request, env, ctx) {
      const sql = Sentry.instrumentPostgresJsSql(postgres(env.DATABASE_URL));
  
      // All queries now create Sentry spans
      const users = await sql`SELECT * FROM users WHERE id = ${userId}`;
      return Response.json(users);
    },
  });

  The instrumentation is available in @sentry/core, @sentry/cloudflare, and @sentry/deno.

• feat(nextjs): Add Turbopack support for thirdPartyErrorFilterIntegration (#​19542)

  We added experimental support for the thirdPartyErrorFilterIntegration with Turbopack builds.

  This feature requires Next.js 16+ and is currently behind an experimental flag:

  // next.config.ts
  import { withSentryConfig } from '@​sentry/nextjs';
  
  export default withSentryConfig(nextConfig, {
    _experimental: {
      turbopackApplicationKey: 'my-app-key',
    },
  });

  Then configure the integration in your client instrumentation file with a matching key:

  // instrumentation-client.ts
  import * as Sentry from '@​sentry/nextjs';
  
  Sentry.init({
    integrations: [
      Sentry.thirdPartyErrorFilterIntegration({
        filterKeys: ['my-app-key'],
        behaviour: 'apply-tag-if-exclusively-contains-third-party-frames',
      }),
    ],
  });

Other Changes

• feat(core,cloudflare): Add dispose to the client for proper cleanup (#​19506)
• feat(deps): Bump rxjs from 7.8.1 to 7.8.2 (#​19545)
• feat(nextjs): Use not: foreign condition in turbopack loaders (#​19502)
• feat(react-router): Include middleware function names and indices (#​19109)
• fix(consola): Normalize extra keys from consola (#​19511)
• fix(core): Improve message truncation for multimodal content and normalize streaming span names (#​19500)
• fix(core): Strip inline media from multimodal content before stringification (#​19540)
• fix(deps): Bump transitive rollup deps to patch CVE-2026-27606 (#​19565)
• fix(langchain): Use runName argument in handleChainStart to fix unknown_chain spans (#​19554)
• fix(nestjs): Improve control flow exception filtering (#​19524)
• fix(tanstackstart-react): Flush events in server entry point for serverless environments (#​19513)
• fix(vue): Avoid triggering deprecated next callback from router instrumentation (#​19476)

Work in this release was contributed by @​YevheniiKotyrlo. Thank you for your contribution!