Important Changes

• feat(elysia): @sentry/elysia - Alpha Release (#19509)

  New Sentry SDK for the Elysia web framework, supporting both Bun and Node.js runtimes.

  Note: This is an alpha release. Please report any issues or feedback on GitHub.

  Features

  • Automatic error capturing — 5xx errors captured via global onError hook; 3xx/4xx ignored by default. Customizable with shouldHandleError.
  • Automatic tracing — Lifecycle spans for every Elysia phase (Request, Parse, Transform, BeforeHandle, Handle, AfterHandle, MapResponse, AfterResponse, Error) with parameterized route names (e.g. GET /users/:id).
  • Distributed tracing — sentry-trace and baggage headers propagated automatically on incoming/outgoing requests.

  Usage

  import * as Sentry from '@sentry/elysia';
  import { Elysia } from 'elysia';
  
  Sentry.init({ dsn: '__DSN__', tracesSampleRate: 1.0 });
  
  const app = Sentry.withElysia(new Elysia());
  app.get('/', () => 'Hello World');
  app.listen(3000);

Other Changes

• feat(nuxt): Conditionally use plugins based on Nitro version (v2/v3) (#19955)
• fix(cloudflare): Forward ctx argument to Workflow.do user callback (#19891)
• fix(cloudflare): Send correct events in local development (#19900)
• fix(core): Do not overwrite user provided conversation id in Vercel (#19903)
• fix(core): Preserve .withResponse() on Anthropic instrumentation (#19935)
• fix(core): Send internal_error as span status for Vercel error spans (#19921)
• fix(core): Truncate content array format in Vercel (#19911)
• fix(deps): bump fast-xml-parser to 5.5.8 in @azure/core-xml chain (#19918)
• fix(deps): bump socket.io-parser to 4.2.6 to fix CVE-2026-33151 (#19880)
• fix(nestjs): Add node to nest metadata (#19875)
• fix(serverless): Add node to metadata (#19878)

Work in this release was contributed by @roli-lpci. Thank you for your contributions!

Bundle size 📦

• fix(v8/browser): Ensure that performance.measure spans have a positive duration (#19959)
• fix(v8/core): Filter gmo error and Facebook mobile error (#15447)

Important Changes

• feat(remix): Server Timing Headers Trace Propagation (#18653)

  The Remix SDK now supports automatic trace propagation via Server-Timing response headers to continue pageload traces on the client side.
  This means, you no longer have to define a custom meta function to add Sentry <meta> tags to your page as previously.
  We'll update out Remix tracing docs after this release.

Other Changes

• fix(cloudflare): Use correct env types for withSentry (#19836)
• fix(core): Align error span status message with core SpanStatusType for langchain/google-genai (#19863)
• fix(deno): Clear pre-existing OTel global before registering TracerProvider (#19723)
• fix(nextjs): Skip tracing for tunnel requests (#19861)
• fix(node-core): Recycle propagationContext for each request (#19835)
• ref(core): Simplify core utility functions for smaller bundle (#19854)

Bundle size 📦

Important Changes

• feat(effect): Add @sentry/effect SDK (Alpha) (#19644)

  This release introduces @sentry/effect, a new SDK for Effect.ts applications. The SDK provides Sentry integration via composable Effect layers for both Node.js and browser environments.

  Compose the effectLayer with optional tracing, logging, and metrics layers to instrument your Effect application:

  import * as Sentry from '@sentry/effect';
  import * as Layer from 'effect/Layer';
  import * as Logger from 'effect/Logger';
  
  const SentryLive = Layer.mergeAll(
    Sentry.effectLayer({ dsn: '__DSN__', tracesSampleRate: 1.0, enableLogs: true }),
    Layer.setTracer(Sentry.SentryEffectTracer),
    Logger.replace(Logger.defaultLogger, Sentry.SentryEffectLogger),
    Sentry.SentryEffectMetricsLayer,
  );

  Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.

• feat(astro): Add Astro 6 support (#19745)

  This release enables full support for Astro v6 by adjusting our Astro SDK's middleware to some Astro-internal
  changes. We cannot yet guarantee full support for server-islands, due to a bug in Astro v6
  but we'll follow up on this once the bug is fixed.

• feat(hono): Add basic instrumentation for Node runtime (#19817)

  Adds a new package @sentry/hono/node (alpha) with basic instrumentation for Hono applications running in Node.js.
  The Hono middleware for Cloudflare (@sentry/hono/cloudflare - alpha) comes with fixes, and it's now possible to access the Cloudflare Worker Bindings (env) from the options' callback.

  Start using the new Hono middlewares by installing @sentry/hono and importing the respective middleware for your runtime.
  More instructions can be found in the Hono readme.

  Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.

• feat(nestjs): Instrument @nestjs/bullmq @Processor decorator (#19759)

  Automatically capture exceptions and create transactions for BullMQ queue processors in NestJS applications.

  When using the @Processor decorator from @nestjs/bullmq, the SDK now automatically wraps the process() method
  to create queue.process transactions with proper isolation scopes, preventing breadcrumb and scope leakage between
  jobs and HTTP requests. Errors thrown in processors are captured with the auto.queue.nestjs.bullmq mechanism type.

  Requires @nestjs/bullmq v10.0.0 or later.

• feat(nestjs): Instrument @nestjs/schedule decorators (#19735)

  Automatically capture exceptions thrown in @Cron, @Interval, and @Timeout decorated methods.

  Previously, exceptions in @Cron methods were only captured if you used the SentryCron decorator. Now they are
  captured automatically. The exception mechanism type changed from auto.cron.nestjs.async to
  auto.function.nestjs.cron. If you have Sentry queries or alerts that filter on the old mechanism type, update them
  accordingly.

• feat(node): Expose headersToSpanAttributes option on nativeNodeFetchIntegration() (#19770)

  Response headers like http.response.header.content-length were previously captured automatically on outgoing
  fetch spans but are now opt-in since @opentelemetry/instrumentation-undici@0.22.0. You can now configure which
  headers to capture via the headersToSpanAttributes option.

  Sentry.init({
    integrations: [
      Sentry.nativeNodeFetchIntegration({
        headersToSpanAttributes: {
          requestHeaders: ['x-custom-header'],
          responseHeaders: ['content-length', 'content-type'],
        },
      }),
    ],
  });

Other Changes

• feat(browser/cloudflare): Export conversation id from browser and cloudflare runtimes (#19820)
• feat(bun): Set http response header attributes instead of response context headers (#19821)
• feat(core): Add sentry.timestamp.sequence attribute for timestamp tie-breaking (#19421)
• feat(deno): Set http response header attributes instead of response context headers (#19822)
• feat(deps): Bump OpenTelemetry dependencies (#19682)
• feat(nestjs): Use more specific span origins for NestJS guards, pipes, interceptors, and exception filters (#19751)
• feat(nextjs): Vercel queue instrumentation (#19799)
• feat(node): Avoid OTEL instrumentation for outgoing requests on Node 22+ (#17355)
• feat(deps): bump hono from 4.12.5 to 4.12.7 (#19747)
• feat(deps): bump mysql2 from 3.14.4 to 3.19.1 (#19787)
• feat(deps): bump simple-git from 3.30.0 to 3.33.0 (#19744)
• feat(deps): bump yauzl from 3.2.0 to 3.2.1 (#19809)
• fix(browser): Skip browserTracingIntegration setup for bot user agents (#19708)
• fix(cloudflare): Recreate client when previous one was disposed (#19727)
• fix(core): Align Vercel embedding spans with semantic conventions (#19795)
• fix(core): Fallback to sendDefaultPii setting in langchain and langgraph in non-node environments (#19813)
• fix(core): Improve Vercel AI SDK instrumentation attributes (#19717)
• fix(hono): Align error mechanism (#19831)
• fix(hono): Allow passing env and fix type issues (#19825)
• fix(nestjs): Fork isolation scope in @nestjs/event-emitter instrumentation (#19725)
• fix(nextjs): Log correct lastEventId when error is thrown in component render (#19764)
• fix(nextjs): Strip sourceMappingURL comments after deleting source maps in turbopack builds (#19814)
• fix(nuxt): Upload client source maps (#19805)
• fix(profiling-node): Fix NODE_VERSION rendered as [object Object] in warning (#19788)

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!

Bundle size 📦

• 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)

Bundle size 📦

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!

Bundle size 📦

This is an internal beta release to test adding traces by timestamp to replay events for EAP trace association: #18048.

Bundle size 📦

Important Changes

• feat(tanstackstart-react): Add global sentry exception middlewares (#19330)

  The sentryGlobalRequestMiddleware and sentryGlobalFunctionMiddleware global middlewares capture unhandled exceptions thrown in TanStack Start API routes and server functions. Add them as the first entries in the requestMiddleware and functionMiddleware arrays of createStart():

  import { createStart } from '@tanstack/react-start/server';
  import { sentryGlobalRequestMiddleware, sentryGlobalFunctionMiddleware } from '@sentry/tanstackstart-react';
  
  export default createStart({
    requestMiddleware: [sentryGlobalRequestMiddleware, myRequestMiddleware],
    functionMiddleware: [sentryGlobalFunctionMiddleware, myFunctionMiddleware],
  });

• feat(tanstackstart-react)!: Export Vite plugin from @sentry/tanstackstart-react/vite subpath (#19182)

  The sentryTanstackStart Vite plugin is now exported from a dedicated subpath. Update your import:

  - import { sentryTanstackStart } from '@sentry/tanstackstart-react';
  + import { sentryTanstackStart } from '@sentry/tanstackstart-react/vite';

• fix(node-core): Reduce bundle size by removing apm-js-collab and requiring pino >= 9.10 (#18631)

  In order to keep receiving pino logs, you need to update your pino version to >= 9.10, the reason for the support bump is to reduce the bundle size of the node-core SDK in frameworks that cannot tree-shake the apm-js-collab dependency.

• fix(browser): Ensure user id is consistently added to sessions (#19341)

  Previously, the SDK inconsistently set the user id on sessions, meaning sessions were often lacking proper coupling to the user set for example via Sentry.setUser().
  Additionally, the SDK incorrectly skipped starting a new session for the first soft navigation after the pageload.
  This patch fixes these issues. As a result, metrics around sessions, like "Crash Free Sessions" or "Crash Free Users" might change.
  This could also trigger alerts, depending on your set thresholds and conditions.
  We apologize for any inconvenience caused!

  While we're at it, if you're using Sentry in a Single Page App or meta framework, you might want to give the new 'page' session lifecycle a try!
  This new mode no longer creates a session per soft navigation but continues the initial session until the next hard page refresh.
  Check out the docs to learn more!

• ref!(gatsby): Drop Gatsby v2 support (#19467)

  We drop support for Gatsby v2 (which still relies on webpack 4) for a critical security update in https://github.com/getsentry/sentry-javascript-bundler-plugins/releases/tag/5.0.0

Other Changes

• feat(astro): Add support for Astro on CF Workers (#19265)
• feat(cloudflare): Instrument async KV API (#19404)
• feat(core): Add framework-agnostic tunnel handler (#18892)
• feat(deno): Export logs API from Deno SDK (#19313)
• feat(deno): Export metrics API from Deno SDK (#19305)
• feat(deno): instrument Deno.serve with async context support (#19230)
• feat(deps): bump babel-loader from 8.2.5 to 10.0.0 (#19303)
• feat(deps): bump body-parser from 1.20.4 to 2.2.2 (#19191)
• feat(deps): Bump hono from 4.11.7 to 4.11.10 (#19440)
• feat(deps): bump qs from 6.14.1 to 6.14.2 (#19310)
• feat(deps): bump the opentelemetry group with 4 updates (#19425)
• feat(feedback): Add setTheme() to dynamically update feedback widget color scheme (#19430)
• feat(nextjs): Add sourcemaps.filesToDeleteAfterUpload as a top-level option (#19280)
• feat(node): Add ignoreConnectSpans option to postgresIntegration (#19291)
• feat(node): Bump to latest @fastify/otel (#19452)
• fix: Bump bundler plugins to v5 (#19468)
• fix: updated the codecov config (#19350)
• fix(aws-serverless): Prevent crash in isPromiseAllSettledResult with null/undefined array elements (#19346)
• fix(bun) Export pinoIntegration from @sentry/node (#17990)
• fix(core,browser): Delete SentryNonRecordingSpan from fetch/xhr map (#19336)
• fix(core): Explicitly flush log buffer in client.close() (#19371)
• fix(core): Langgraph state graph invoke accepts null to resume (#19374)
• fix(core): Wrap decodeURI in node stack trace parser to handle malformed URIs (#19400)
• fix(deps): Bump nuxt devDependency to fix CVE-2026-24001 (#19249)
• fix(deps): Bump to latest version of each minimatch major (#19486)
• fix(nextjs): Apply environment from options if set (#19274)
• fix(nextjs): Don't set sentry.drop_transaction attribute on spans when skipOpenTelemetrySetup is enabled (#19333)
• fix(nextjs): Normalize trailing slashes in App Router route parameterization (#19365)
• fix(nextjs): Return correct lastEventId for SSR pages (#19240)
• fix(nextjs): Set parameterized transaction name for non-transaction events (#19316)
• fix(node-core): Align pino mechanism type with spec conventions (#19363)
• fix(nuxt): Use options.rootDir instead of options.srcDir (#19343)

This preview release includes updates to our Span Streaming PoC implementation. Use at your own risk.

New:

• Browser: SDKs now also use a span buffer, flushing periodically, on span amount limit and on segment span end
• Browser: It's now enough to only register spanStreamingIntegration in Sentry.init.() to opt into span streaming
• Browser: sentry.replay_id attribute is attached to spans started during an active replay
• Browser: sentry.profiler_id attribute is attached to spans started while the continuous profiler is running
• Browser: Web vital spans are sent as v2 spans
• Browser: spanStreamingIntegration is now exported from CDN bundles supporting tracing

Known issues:

• Missing data from various integrations and framework SDKs
• ignoreSpans is not yet applied

Untested:

• Meta frameworks or framework SDKs building on top of @sentry/browser or @sentry/node. Likely, data is missing, noisy spans are not filtered, etc.

Usage (At your own risk)

Browser

Sentry.init({
  dsn: '...',
  integrations: [
    Sentry.browserTracingIntegration(),
    Sentry.spanStreamingIntegration(),
  ]
})

Server (Node)

Sentry.init({
  dsn: '...',
  traceLifecycle: 'stream',
})

Bundle size 📦