@sentry/ember

• deprecated

  replay/v9: Deprecate _experiments.autoFlushOnFeedback

• v9/core: Add shared flushIfServerless function

• v9/react-router: Add createSentryHandleError

• v9/react-router: Automatically flush on serverless for loaders/actions

• v9/react-router: Automatically flush on serverless for request handler

• v9/astro: Construct parametrized route during runtime

• v9/nextjs: Flush in route handlers

• v9/node: Fix exports for openai instrumentation

Bundle size

• v9/core: Add MCP server instrumentation

• v9/meta: Unify detection of serverless environments and add Cloud Run

• v9/node: Add mechanism to fastifyIntegration error handler

• v9/replay: Fix re-sampled sessions after a click

Bundle size

• v9/aws: Detect SDK source for AWS Lambda layer

• v9/core: Fix OpenAI SDK private field access by binding non-instrumented fns

• v9/core: Update ai.response.object to gen_ai.response.object

• v9/nextjs: Update stackframe calls for next v15.5

Bundle size

Important Changes

• deprecated

  v9/core: Deprecate experimental enableLogs and beforeSendLog option

Sentry now has support for structured logging. Previously to enable structured logging, you had to use the _experiments.enableLogs and _experiments.beforeSendLog options. These options have been deprecated in favor of the top-level enableLogs and beforeSendLog options.

// before
Sentry.init({
  _experiments: {
    enableLogs: true,
    beforeSendLog: log => {
      return log;
    },
  },
});

// after
Sentry.init({
  enableLogs: true,
  beforeSendLog: log => {
    return log;
  },
});

• astro: Implement parameterized routes

  • feat(v9/astro): Parametrize dynamic server routes

  • feat(v9/astro): Parametrize routes on client-side

Server-side and client-side parameterized routes are now supported in the Astro SDK. No configuration changes are required.

Other Changes

• v9/node: Add shouldHandleError option to fastifyIntegration

• fix(v9/cloudflare) Allow non UUID workflow instance IDs

• v9/node: Ensure tool errors for vercelAiIntegration have correct trace

• v9/remix: Ensure source maps upload fails silently if Sentry CLI fails

• v9/svelte: Do not insert preprocess code in script module in Svelte 5

Work in this release was contributed by @richardjelinek-fastest. Thank you for your contribution!

Bundle size

Important Changes

• browser: Add debugId sync APIs between web worker and main thread

This release adds two Browser SDK APIs to let the main thread know about debugIds of worker files:

• webWorkerIntegration({worker}) to be used in the main thread

• registerWebWorker({self}) to be used in the web worker

// main.js
Sentry.init({...})

const worker = new MyWorker(...);

Sentry.addIntegration(Sentry.webWorkerIntegration({ worker }));

worker.addEventListener('message', e => {...});

// worker.js
Sentry.registerWebWorker({ self });

self.postMessage(...);

• deprecated

  core: Deprecate logger in favor of debug

The internal SDK logger export from @sentry/core has been deprecated in favor of the debug export. debug only exposes log, warn, and error methods but is otherwise identical to logger. Note that this deprecation does not affect the logger export from other packages (like @sentry/browser or @sentry/node) which is used for Sentry Logging.

import { logger, debug } from '@sentry/core';

// before
logger.info('This is an info message');

// after
debug.log('This is an info message');

• node: Add OpenAI integration

This release adds official support for instrumenting OpenAI SDK calls in with Sentry tracing, following OpenTelemetry semantic conventions for Generative AI. It instruments:

• client.chat.completions.create() - For chat-based completions

• client.responses.create() - For the responses API

// The integration respects your `sendDefaultPii` option, but you can override the behavior in the integration options

Sentry.init({
  dsn: '__DSN__',
  integrations: [
    Sentry.openAIIntegration({
      recordInputs: true, // Force recording prompts
      recordOutputs: true, // Force recording responses
    }),
  ],
});

Other Changes

• node-core: Expand @opentelemetry/instrumentation range to cover 0.203.0

• cloudflare: Ensure errors get captured from durable objects

• sveltekit: Ensure server errors from streamed responses are sent

Work in this release was contributed by @0xbad0c0d3 and @tommy-gilligan. Thank you for your contributions!

Bundle size

Important Changes

• browser: Add afterStartPageloadSpan hook to improve spanId assignment on web vital spans

This PR adds a new afterStartPageloadSpan lifecycle hook to more robustly assign the correct pageload span ID to web vital spans, replacing the previous unreliable "wait for a tick" approach with a direct callback that fires when the pageload span becomes available.

• nextjs: Client-side parameterized routes

This PR implements client-side parameterized routes for Next.js by leveraging an injected manifest within the existing app-router instrumentation to automatically parameterize all client-side transactions (e.g. users/123 and users/456 now become become users/:id).

• node: Drop 401-404 and 3xx status code spans by default

This PR changes the default behavior in the Node SDK to drop HTTP spans with 401-404 and 3xx status codes by default to reduce noise in tracing data.

Other Changes

• core: Prepend vercel ai attributes with vercel.ai.X

• nextjs: Add disableSentryWebpackConfig flag

• nextjs: Build app manifest

• nextjs: Inject manifest into client for turbopack builds

• nextjs: Inject manifest into client for webpack builds

• node-native: Add option to disable event loop blocked detection

• react-router: Ensure http.server route handling is consistent

• core: Avoid prolonging idle span when starting standalone span

• core: Remove side-effect from tracing/errors.ts

• core: Wrap beforeSendLog in consoleSandbox

• node-core: Apply correct SDK metadata

• react-router: Ensure that all browser spans have source=route

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

Bundle size

Important Changes

This release publishes the @sentry/node-native SDK.

Other Changes

• core: Introduce debug to replace logger

• browser: Guard nextHopProtocol when adding resource spans

Bundle size

Important Changes

• nuxt: Parametrize SSR routes

  When requesting dynamic or catch-all routes in Nuxt, those will now be shown as parameterized routes in Sentry.
  For example, /users/123 will be shown as /users/:userId() in Sentry. This will make it easier to identify patterns and make grouping easier.

Other Changes

• deprecated

  astro: Deprecate passing runtime config to astro integration

• browser: Add beforeStartNavigationSpan lifecycle hook

• browser: Detect redirects when emitting navigation spans

• cloudflare: Add option to opt out of capturing errors in wrapRequestHandler

• feedback: Return the eventId into the onSubmitSuccess callback

• vercel-edge: Do not vendor in all OpenTelemetry dependencies

• browser: Ensure standalone CLS and LCP spans have traceId of pageload span

• nextjs: Use value injection loader on instrumentation-client.ts|js

• sveltekit: Avoid capturing redirect() calls as errors in Cloudflare

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

Bundle size

Important Changes

• node-core: Add node-core SDK

This release adds a new SDK @sentry/node-core which ships without any OpenTelemetry instrumententation out of the box. All OpenTelemetry dependencies are peer dependencies and OpenTelemetry has to be set up manually.

Use @sentry/node-core when:

• You already have OpenTelemetry set up

• You need custom OpenTelemetry configuration

• You want minimal dependencies

• You need fine-grained control over instrumentation

Use @sentry/node when:

• You want an automatic setup

• You're new to OpenTelemetry

• You want sensible defaults

• You prefer convenience over control

• deprecated

  node: Deprecate ANR integration

The ANR integration has been deprecated and will be removed in future versions. Use eventLoopBlockIntegration from @sentry/node-native instead.

• replay: Add _experiments.ignoreMutations option

This replay option allows to configure a selector list of elements to not capture mutations for.

Sentry.replayIntegration({
  _experiments: {
    ignoreMutations: ['.dragging'],
  },
});

Other changes

• nextjs: Add flag for suppressing router transition warning

• nextjs: Automatically skip middleware requests for tunnel route

• replay: Export compression worker from @sentry/replay-internal

• browser: Avoid 4xx response for succesful diagnoseSdkConnectivity request

• browser: Guard against undefined nextHopProtocol

• cloudflare: Calculate retries not attempts

• nuxt: Parametrize routes on the server-side

• vue: Make pageload span handling more reliable

Work in this release was contributed by @Spice-King and @stayallive. Thank you for your contributions!

Bundle size

• browser: Add ElementTiming instrumentation and spans

• browser: Export Context and Contexts types

• cloudflare: Add user agent to cloudflare spans

• node: Add eventLoopBlockIntegration

• node: Export server-side feature flag integration shims

• node: Update vercel ai integration attributes

• astro: Handle errors in middlewares better

• browser: Ensure explicit parentSpan is considered

• node: Avoid using dynamic require for fastify integration

• nuxt: Add @sentry/cloudflare as optional peerDependency

• nuxt: Ensure order of plugins is consistent

• nestjs: Fix exception handling in @Cron decorated tasks

Work in this release was contributed by @0xbad0c0d3 and @alSergey. Thank you for your contributions!

Bundle size

Important Changes

• Add opt-in vercelAiIntegration to cloudflare & vercel-edge

The vercelAiIntegration is now available as opt-in for the Cloudflare and the Next.js SDK for Vercel Edge.
To use it, add the integration in Sentry.init

Sentry.init({
  tracesSampleRate: 1.0,
  integrations: [Sentry.vercelAIIntegration()],
});

And enable telemetry for Vercel AI calls

const result = await generateText({
  model: openai('gpt-4o'),
  experimental_telemetry: {
    isEnabled: true,
  },
});

• node: Add postgresjs instrumentation

The Node.js SDK now includes instrumentation for Postgres.js.

• node: Use diagnostics channel for Fastify v5 error handling

If you're on Fastify v5, you no longer need to call setupFastifyErrorHandler. It is done automatically by the node SDK. Older versions still rely on calling setupFastifyErrorHandler.

Other Changes

• cloudflare: Allow interop with OpenTelemetry emitted spans

• cloudflare: Flush after waitUntil

• nextjs: Remove ai from default server external packages

Work in this release was contributed by @0xbad0c0d3. Thank you for your contribution!

Bundle size

Important Changes

• browser: Add CLS sources to span attributes

Enhances CLS (Cumulative Layout Shift) spans by adding attributes detailing the elements that caused layout shifts.

• cloudflare: Add instrumentWorkflowWithSentry to instrument workflows

We've added support for Cloudflare Workflows, enabling comprehensive tracing for your workflow runs. This integration uses the workflow's instanceId as the Sentry trace_id and for sampling, linking all steps together. You'll now be able to see full traces, including retries with exponential backoff.

• pino-transport: Add functionality to send logs to sentry

Adds the ability to send logs to Sentry via a pino transport.

Other Changes

• nextjs: Expose top level buildTime errorHandler option

• node: Update pipeline spans to use agent naming

• sveltekit: Export logger from sveltekit worker

• google-cloud-serverless: Make CloudEventsContext compatible with CloudEvent

• nextjs: Stop injecting release value when create release options is set to false

• node: Account for Object. syntax with local variables matching

• nuxt: Add alias for @opentelemetry/resources

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

Bundle size

Important Changes

• nextjs: Add option for auto-generated random tunnel route

Adds an option to automatically generate a random tunnel route for the Next.js SDK. This helps prevent ad blockers and other tools from blocking Sentry requests by using a randomized path instead of the predictable /monitoring endpoint.

• core: Allow to pass scope & client to getTraceData

Adds the ability to pass custom scope and client parameters to the getTraceData function, providing more flexibility when generating trace data for distributed tracing.

Other Changes

• core: Add support for x-forwarded-host and x-forwarded-proto headers

• flags: Add node support for generic featureFlagsIntegration and move utils to core

• flags: Capture feature flag evaluations on spans

• pino: Add initial package for @sentry/pino-transport

• Wait for the correct clientWidth/clientHeight when showing Feedback Screenshot previews

• removed

  browser: Remove usage of Array.at() method

• core: Improve safeJoin usage in console logging integration

• google-cloud-serverless: Make CloudEvent type compatible

• nextjs: Fix lookup of instrumentation-client.js file

• node: Ensure graphql errors result in errored spans

Bundle size

• nextjs: Add URL to tags of server components and generation functions issues

• nextjs: Ensure all packages we auto-instrument are externalized

• node: Automatically enable vercelAiIntegration when ai module is detected

• node: Ensure modulesIntegration works in more environments

• core: Don't gate user on logs with sendDefaultPii

• browser: Add detail to measure spans and add regression tests

• node: Update Vercel AI span attributes

• opentelemetry: Ensure only orphaned spans of sent spans are sent

Bundle size

Important Changes

This release upgrades the web-vitals library to version 5.0.2. This upgrade could slightly change the collected web vital values and potentially also influence alerts and performance scores in the Sentry UI.

Other Changes

• ember: Stop warning for onError usage

• node: Allow to force activate vercelAiIntegration

• node: Introduce ignoreLayersType option to koa integration

• browser: Ensure suppressTracing does not leak when async

• vue: Ensure root component render span always ends

Bundle size

Important Changes

• nestjs: Stop creating spans for TracingInterceptor

With this change we stop creating spans for TracingInterceptor as this interceptor only serves as an internal helper and adds noise for the user.

• node: Update vercel ai spans as per new conventions

This feature ships updates to the span names and ops to better match OpenTelemetry. This should make them more easily accessible to the new agents module view we are building.

Other Changes

• sveltekit: Export vercelAIIntegration from @sentry/node

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

Bundle size

• node: Expand how vercel ai input/outputs can be set

• node: Switch to new semantic conventions for Vercel AI

• react-router: Add component annotation plugin

• react-router: Export wrappers for server loaders and actions

• browser: Ignore unrealistically long INP values

• react-router: Conditionally add ReactRouterServer integration

Bundle size

Important Changes

• browser: Add option to ignore mark and measure spans

This release adds an option to browserTracingIntegration that lets you ignore
mark and measure spans created from the performance.mark(...) and performance.measure(...) browser APIs:

Sentry.init({
  integrations: [
    Sentry.browserTracingIntegration({
      ignorePerformanceApiSpans: ['measure-to-ignore', /mark-to-ignore/],
    }),
  ],
});

Other Changes

• browser: Export getTraceData from the browser sdks

• node: Add includeServerName option

• nuxt: Remove setting @sentry/nuxt external

Bundle size

Important Changes

• angular: Bump @sentry/angular peer dependencies to add Angular 20 support

This release adds support for Angular 20 to the Sentry Angular SDK @sentry/angular.

Other Changes

• browser: Add unregisterOriginalCallbacks option to browserApiErrorsIntegration

• core: Add user to logs

• core: Make sure Supabase db query insights are populated

Bundle size

Important changes

• browser: Option to ignore certain resource types

Adds an option to opt out of certain resource.* spans via ignoreResourceSpans.

For example, to opt out of resource.script spans:

Sentry.browserTracingIntegration({
  ignoreResourceSpans: ['resource.script'],
}),

Other changes

• Export isEnabled from all SDKs

• browser: Disable client when browser extension is detected in init()

• core: Allow re-use of captureLog

• core: Export _INTERNAL_captureSerializedLog

• nextjs: Include static/chunks/main-* files for widenClientFileUpload

• node: Do not add HTTP & fetch span instrumentation if tracing is disabled

• nuxt: Added support for nuxt layers

• browser: Ensure logs are flushed when sendClientReports=false

• browser: Move browserTracingIntegration code to setup hook

• cloudflare: Capture exceptions thrown in hono

• node: Don't warn about Spotlight on empty NODE_ENV

• node: Suppress Spotlight calls

• nuxt: Add @sentry/nuxt as external in Rollup

• opentelemetry: Ensure withScope keeps span active & _getTraceInfoFromScope works

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

Bundle size

Important changes

• Revert "feat(browser): Track measure detail as span attributes"

This is a revert of a feature introduced in 9.20.0 with #16240. This feature was causing crashes in firefox, so we are reverting it. We will re-enable this functionality in the future after fixing the crash.

Other changes

• remix: Use generic types for ServerBuild argument and return

Bundle size

• node: Vendor in @fastify/otel

• nestjs: Handle multiple OnEvent decorators

• node: Avoid creating breadcrumbs for suppressed requests

• remix: Add missing client exports to server and cloudflare entries

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

Bundle size

Important changes

• browser: Track measure detail as span attributes

The SDK now automatically collects details passed to performance.measure options.

Other changes

• node: Add maxIncomingRequestBodySize

• react-router: Add server action instrumentation

• react-router: Filter manifest requests

• replay: Extend default list for masking with aria-label

• browser: Ensure pageload & navigation spans have correct data

• cloudflare: Account for static fields in wrapper type

• nextjs: Preserve next.route attribute on root spans

• node: Fork isolation scope in tRPC middleware

• core: Add orgId option to init and DSC (sentry-org_id in baggage)

Bundle size

• react-router: Add otel instrumentation for server requests

• remix: Vendor in opentelemetry-instrumentation-remix

• browser: Ensure spans auto-ended for navigations have cancelled reason

• node: Pin @fastify/otel fork to direct url to allow installing without git

• react: Handle nested parameterized routes in reactrouterv3 transaction normalization

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

Bundle size

Important changes

• Support Node 24

We now also publish profiling binaries for Node 24.

Other changes

• Export consoleLoggingIntegration from vercel edge sdk

• cloudflare: Add support for email, queue, and tail handler

• cloudflare: Improve http span data

• nextjs: Add more attributes for generation functions

• opentelemetry: Widen peer dependencies to support Otel v2

• core: Gracefully handle invalid baggage entries

• node: Ensure traces are propagated without spans in Node 22+

• node: Use sentry forked @fastify/otel dependency with pinned Otel v1 deps

• remix: Remove vendored types

Bundle size

Important changes

• Create a Vite plugin that injects sentryConfig into the global config

Add a new plugin makeConfigInjectorPlugin within our existing vite plugin that updates the global vite config with sentry options

• browser: Add option to sample linked traces consistently

This PR implements consistent sampling across traces as outlined in

• cloudflare: Add support for durable objects

This PR introduces a new instrumentDurableObjectWithSentry method to the SDK, which instruments durable objects. We capture both traces and errors automatically.

• node: Add Prisma integration by default

Prisma integration is enabled by default, it should work for both ESM and CJS.

• react-router: Add client-side router instrumentation

Adds client-side instrumentation for react router's HydratedRouter. To enable it, simply replace browserTracingIntegration() with reactRouterTracingIntegration() in your client-side init call.

• node: Avoid double-wrapping http module

When running your application in ESM mode, there have been scenarios that resulted in the http/https emitting duplicate spans for incoming requests. This was apparently caused by us double-wrapping the modules for incoming request isolation.

In order to solve this problem, the modules are no longer monkey patched by us for request isolation. Instead, we register diagnosticschannel hooks to handle request isolation now.
While this is generally not expected to break anything, there is one tiny change that _may affect you if you have been relying on very specific functionality:

The ignoreOutgoingRequests option of httpIntegration receives the RequestOptions as second argument. This type is not changed, however due to how the wrapping now works, we no longer pass through the full RequestOptions, but re-construct this partially based on the generated request. For the vast majority of cases, this should be fine, but for the sake of completeness, these are the only fields that may be available there going forward - other fields that may have existed before may no longer be set:

ignoreOutgoingRequests(url: string, {
  method: string;
  protocol: string;
  host: string;
  hostname: string; // same as host
  path: string;
  headers: OutgoingHttpHeaders;
})

Other changes

• cloudflare: Add logs exports

• vercel-edge: Add logs export

• cloudflare: Read SENTRY_RELEASE from env

• node: Drop http.server spans with 404 status by default

• browser: Respect manually set sentry tracing headers in XHR requests

• core: Respect manually set sentry tracing headers in fetch calls

• feedback: Prevent removeFromDom() from throwing

• node: Use class constructor in docstring for winston transport

• node: Fix vercel flushing logic & add test for it

• node: Fix 404 route handling in express 5

• logs: Ensure logs can be flushed correctly

Bundle size

Important Changes

• Export wrapMcpServerWithSentry from server packages

Exports the wrapMcpServerWithSentry which is our MCP server instrumentation from all the server packages.

• core: Associate resource/tool/prompt invocations with request span instead of response span

Adds a best effort mechanism to associate handler spans for resource, tool and prompt with the incoming message requests instead of the outgoing SSE response.

Other Changes

• Vercel ai ESM patching

• node: Update version range for module.register

• react-router: Spread unstable_sentryVitePluginOptions correctly

• react: Fix Redux integration failing with reducer injection

• remix: Add ESM-compatible exports

• remix: Avoid rewrapping root loader.

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

Bundle size

Important Changes

• Add Supabase Integration

This PR adds Supabase integration to @sentry/core, allowing automatic instrumentation of Supabase client operations (database queries and authentication) for performance monitoring and error tracking.

• nestjs: Gracefully handle RPC scenarios in SentryGlobalFilter

This PR adds better RPC exception handling to @sentry/nestjs, preventing application crashes while still capturing errors and warning users when a dedicated filter is needed. The implementation gracefully handles the 'rpc' context type in SentryGlobalFilter to improve reliability in hybrid applications.

• react-router: Trace propagation

This PR adds trace propagation to @sentry/react-router by providing utilities to inject trace meta tags into HTML headers and offering a pre-built Sentry-instrumented request handler, improving distributed tracing capabilities across page loads.

Other Changes

• nextjs: Improve server component data

• nuxt: Log when adding HTML trace meta tags

• node: Make body capturing more robust

Bundle size

Important Changes

• node: Add support for winston logger

  Sentry is adding support for structured logging. In this release we've added support for sending logs to Sentry via the winston logger to the Sentry Node SDK (and SDKs that use the Node SDK under the hood like @sentry/nestjs). The Logging APIs in the Sentry SDK are still experimental and subject to change.

  const winston = require('winston');
  const Transport = require('winston-transport');
  
  const transport = Sentry.createSentryWinstonTransport(Transport);
  
  const logger = winston.createLogger({
    transports: [transport],
  });

• core: Add wrapMcpServerWithSentry to instrument MCP servers from @modelcontextprotocol/sdk

  The Sentry SDK now supports instrumenting MCP servers from the @modelcontextprotocol/sdk package. Compatible with versions ^1.9.0 of the @modelcontextprotocol/sdk package.

  import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
  
  // Create an MCP server
  const server = new McpServer({
    name: 'Demo',
    version: '1.0.0',
  });
  
  // Use the instrumented server in your application
  const instrumentedServer = Sentry.wrapMcpServerWithSentry(server);

• core: Move console integration into core and add to cloudflare/vercel-edge

  Console instrumentation has been added to @sentry/cloudflare and @sentry/nextjs Edge Runtime and is enabled by default. Now calls to the console object will be captured as breadcrumbs for those SDKs.

• bun: Support new Bun.serve APIs

  Bun 1.2.6 and above have a new Bun.serve API, which the Bun SDK now supports. The SDK instruments the new routes object that can be used to define routes for the server.

Other Changes

• browser: Warn on duplicate browserTracingIntegration

• core: Allow delayed sending with offline transport

• vue: Apply stateTransformer to attachments in Pinia Plugin

• core: Run beforeSendLog after we process log

• nextjs: Don't show turbopack warning for newer Next.js canaries

• nextjs: Include patch version 0 for min supported 15.3.0

• node: Ensure late init works with all integrations

• react-router: Pass unstable_sentryVitePluginOptions to cli instance

• serverless-aws: Overwrite root span name with GraphQL if set

Bundle size