@sentry/ember

Important Changes

• Add a managed tunnel that the SDK derives from the DSN (#25199, #25200, #25783)

  Set tunnel: true in your browser Sentry.init call to send events through your own server. This helps when ad blockers block requests to Sentry. The browser derives the tunnel path from the DSN, so older and newer builds of your client and server always agree on the path.

  To serve the tunnel, add serveTunnelIntegration() to your server SDK. Astro, Nuxt, Nitro, React Router, Remix 3, SolidStart, SvelteKit and TanStack Start then answer tunnel requests automatically:

  // browser
  Sentry.init({ dsn, tunnel: true });
  
  // server
  Sentry.init({ dsn, integrations: [Sentry.serveTunnelIntegration()] });

  If the browser uses a different DSN than the server, set serveTunnelIntegration({ allowedDsns: [browserDsn] }). For other setups, the server SDKs export handleTunnelRequestIfMatched, handleTunnelRequest, isTunnelRequest and getTunnelPath:

  app.use((req, res, next) => Sentry.handleTunnelRequestIfMatched(req, res) ?? next());

  The request option of handleTunnelRequest is deprecated and will be removed in v12.

• Make span origins spec compliant

  Some span origins changed their names to follow the trace origin spec:

  • auto.amqplib.* is now auto.queue.amqplib.*, and auto.kafkajs.* is now auto.queue.kafkajs.*.

  • auto.vercelai.channel is now auto.ai.vercelai.

  • auto.firebase.firestore is now auto.db.firebase.firestore, and auto.firebase.functions is now auto.function.firebase.

  • auto.aws.aws_sdk is now auto.{rpc,db,queue,ai}.aws_sdk, with the category from the span op.

  • auto.aws_lambda is now auto.function.aws_serverless.

  • auto.mcp.notification is now auto.function.mcp_server.notification.

  • auto.db.cloudflare.durable_object.sql is now auto.db.cloudflare.durable_object_sql.

  • auto.http.browser.{lcp,cls,inp} is now auto.ui.browser.{lcp,cls,inp}.

  If you have ignoreSpans rules, queries or alerts on the old origins, change them to use the new origins.

• bun: Add incoming request options and request sessions to bunServerIntegration

  bunServerIntegration now accepts the same options as denoServeIntegration: ignoreRequestBody, ignoreIncomingRequests, ignoreStaticAssets, spans, onSpanCreated, onSpanEnd, sessions and sessionFlushingDelayMS. The callbacks receive the web Request.

  Bun.serve now records a request session for each incoming request. Sessions are sent only when a release is set. To turn them off, set bunServerIntegration({ sessions: false }).

  ignoreStaticAssets defaults to true, so Bun.serve no longer creates spans for GET requests to common static assets such as favicon.ico, robots.txt or *.js files. To keep these spans, set bunServerIntegration({ ignoreStaticAssets: false }). Bun.serve spans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled. Errors thrown for OPTIONS and HEAD requests are now captured.

• bun: Inject debug IDs and upload source maps in sentryBunPlugin

  sentryBunPlugin from @sentry/bun/plugin now accepts the same options as sentryEsbuildPlugin (org, project, authToken, release, sourcemaps, ...). When Bun.build writes source maps to outdir, the plugin injects the debug ID that Bun writes into each bundle, injects the release, and uploads the source maps at the end of the build. You no longer need to run sentry sourcemap inject and sentry sourcemap upload after the build.

  Like the other bundler plugins, sentryBunPlugin now sends build telemetry and injects the release it detects (for example, from git). To turn off telemetry, set telemetry: false.

• cloudflare: Add incoming request span options to httpServerIntegration

  Cloudflare's httpServerIntegration now accepts ignoreIncomingRequests, ignoreStaticAssets, spans, onSpanCreated and onSpanEnd, with the same meaning as in the Node, Deno and Bun integrations. The callbacks receive the web Request.

  ignoreStaticAssets defaults to true, so workers no longer create spans for GET requests to common static assets such as favicon.ico, robots.txt or *.js files. To keep these spans, set httpServerIntegration({ ignoreStaticAssets: false }). Request spans also follow the client's tracing configuration by default, so the SDK does not start them when tracing is disabled. If ignoreRequestBody throws, the request no longer fails, and the SDK skips the body.

• cloudflare: Let users configure the channel integrations

  When the @sentry/cloudflare/vite plugin bundles an instrumented package (for example pg or openai), the SDK adds the matching integration with its default options. @sentry/cloudflare now exports these integrations, so you can set their options, for example in instrument.server.ts:

  export default Sentry.defineCloudflareOptions(env => ({
    dsn: env.SENTRY_DSN,
    integrations: [Sentry.openAIIntegration({ recordInputs: false, recordOutputs: false })],
  }));

  These integrations need the vite plugin. Without it, they record nothing, and with debug: true the SDK logs a warning.

• node: Add onSpanEnd to httpIntegration

  httpIntegration and httpServerSpansIntegration now accept onSpanEnd, a hook that runs when the response for an incoming request finishes, before its span ends. Use it to change the span based on the response. Deno and Bun already have this option.

• node, bun, deno, cloudflare: Align portable exports across server SDKs

  Node, Bun, Deno and Cloudflare now export the same helpers from @sentry/core and @sentry/server-utils where they work on that runtime:

  • Node and Bun now export moduleMetadataIntegration, instrumentPostgresJsSql, instrumentCreateReactAgent, awsIntegration and the FlueOptions type. awsIntegration was already in their default integrations.

  • Deno and Cloudflare now export parameterize and instrumentStateGraphCompile.

  • Bun and Cloudflare now export the Log and LogSeverityLevel types.

  • Deno now exports fastifyIntegration, which was already in its default integrations.

• nuxt: Start the server SDK on the Nuxt Vite server (experimental)

  Sentry now supports Node.js production builds using Nuxt 4.6's experimental Vite server (server: { builder: 'vite' }). Your sentry.server.config loads automatically, enabling request tracing and automatic database spans for supported libraries.

  Development mode, Cloudflare, automatic capture of server rendering errors, and connecting server and browser traces via HTML meta tags are not yet supported. This experimental support may change in minor releases.

Other Changes

• Export the Node bundler plugins from SDKs that wrap @sentry/node

• cloudflare: Instrument Workers KV bindings

• nextjs: Warn when Next.js production builds miss the instrumentation file

• react-router: Support renderToReadableStream in createSentryHandleRequest

• server-utils: Emit execute_tool spans for Anthropic's beta.sessions.events.toolRunner()

• server-utils: Record Workers AI Clairic calls as gen_ai.extract spans

• server-utils: Instrument together-ai 1.x

• browser: Preserve empty stacks in continuous profiles

• browser: Resolve request URLs against location.href in tracing

• build: Make CJS re-exports visible to Node ESM imports

• bun: Add systemErrorIntegration to default integrations

• cloudflare: Bind a default re-export with var in the Vite transform

• cloudflare: Do not add back channel integrations the user removed

• cloudflare: Skip comments when locating the default keyword in the Vite transform

• core: Allow project arrays in framework build options

• core: Drop sampled-out errors before they take a promise buffer slot

• core: End node:http client spans when the response is destroyed

• core: Preserve AI proxy property references

• core: Resolve relative URLs when enhancing fetch error messages

• feedback: Wait for frames without the form before capturing the screenshot

• hono: Make the Hono middleware types compile on Hono 5

• node: Flush buffered streamed spans on process exit

• node: Read module versions from the isolated layouts of pnpm and Bun

• node: Set the eve conversation id on model.started for eve 0.84+

• node: Skip spans for outgoing requests to Sentry via undici fetch and node:http

• node: Use the request method for Hapi routes with multiple methods

• nuxt,nitro: Accept Nitro 3 betas without narrowing peer support

• opentelemetry: Convert OpenTelemetry performance.now() timestamps

• react: Avoid double slashes in manifest route names

• react: Parameterize React Router transactions with encoded params

• remix: Drop Remix 3 release candidates from the peer range

• replay: Apply attribute masking to breadcrumb messages

• server-utils: Cap the runs the LangChain callback handler keeps open

• server-utils: Keep OpenAI streamed tool calls that have no index

• server-utils: Keep OpenRouter evaluation confidence and legend on Vercel AI spans

• server-utils: Nest Flue runs on Node under the request that dispatched them

• server-utils: Record AI SDK tool spans for tools run outside its tool loop

• server-utils: Use cumulative input and cache token counts from streamed message_delta

• server-utils: Use the stored pi-durable session id as conversation id

• tanstackstart-react: Unminify server errors in Nitro builds

Internal Changes

• Remove permissions from settings.json

Work in this release was contributed by @4ktLuffy, @faizansaiyed123, @itisrmk, @kunal649, @kyrylolvov, @larcane97, @lfantone, @pcbeingused333, @psh4607, and @seongwon030. Thank you for your contributions!

Bundle size

Important Changes

• Rename diagnostic_channel, fetch and gRPC span origins

  Some span origins changed their names to match the other v11 origins:

  • auto.graphql.diagnostic_channel is now auto.graphql.graphql.

  • auto.db.redis.diagnostic_channel, auto.db.mysql2.diagnostic_channel and auto.db.mongoose.diagnostic_channel now end in .native_channel.

  • auto.http.wintercg_fetch is now auto.http.fetch, as on Bun, Deno and Cloudflare.

  • auto.grpc.serverless is now auto.grpc.google_cloud.

  If you have ignoreSpans rules, queries or alerts on the old origins, change them to use the new origins.

• deno: Add incoming request options to denoServeIntegration

  denoServeIntegration now accepts ignoreRequestBody, ignoreIncomingRequests, ignoreStaticAssets, spans, onSpanCreated and onSpanEnd, with the same meaning as in denoHttpIntegration. The callbacks receive the web Request.

  ignoreStaticAssets defaults to true, so Deno.serve no longer creates spans for GET requests to common static assets such as favicon.ico, robots.txt or *.js files. To keep these spans, set denoServeIntegration({ ignoreStaticAssets: false }). Deno.serve spans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled.

• deno: Record request sessions for Deno.serve

  denoServeIntegration now records a request session for each incoming request, as denoHttpIntegration does for node:http. This gives release health and crash-free rates for Deno.serve apps. Sessions are sent only when a release is set. To turn them off, set denoServeIntegration({ sessions: false }). sessionFlushingDelayMS sets how long the SDK waits before it sends the session aggregate.

• deno: Register channel injection hooks from init()

  Sentry.init() in @sentry/deno now registers the diagnostics-channel injection hooks, as @sentry/node does. The channel integrations now record spans without --preload=npm:@sentry/deno/import, for modules that you import after init(). To also instrument modules that load before init(), such as static imports in your entry module, keep the preload. With debug: true, the SDK logs a warning when no injection is active.

  On Node.js, tracing-hooks messages now show with debug: true instead of with DEBUG=@apm-js-collab/*.

• nextjs: Add a tunnel route handler that sends only the event payload to Sentry

  The tunnelRoute option can now send events through a route handler in your app. The handler forwards only the event payload to Sentry, and no request headers. To use it, add this file next to your tunnelRoute option:

  // app/sentry-tunnel/route.ts (or src/app/sentry-tunnel/route.ts)
  export { POST } from '@sentry/nextjs/tunnel';

  The handler accepts events for the DSN of your server SDK. To accept other DSNs, use createSentryTunnelRoute({ allowedDsns }) from the same import. Without the file, the tunnel route works as before.

  Also, the server no longer sends spans of tunnel requests when span streaming is on, because these spans only show the SDK's own traffic.

• nextjs: Never emit trace meta tags from a prerender

  Pageloads of apps with cacheComponents enabled are connected to their server request again. Pages that Next.js prerenders no longer carry trace information, so a cached page can no longer connect visitors to a request that was not theirs. This also applies to ISR pages. The pageload waits for the trace information when it arrives with the part of the page that streams in after a cached shell.

  If you set up OpenTelemetry yourself and register SentryPropagator, register NextSentryPropagator instead and pass your tracer provider to markPrerendersOnTracerProvider, so that your prerendered pages carry no trace information either.

• nextjs: Send tunnel route requests with credentials: 'omit'

  With tunnelRoute and no tunnel route handler, @sentry/nextjs now sends events from the browser with credentials: 'omit', because the tunnel route does not need cookies.
  If a layer in front of your app checks cookies before it lets requests through (for example Vercel Deployment Protection), you can send them again in your browser Sentry.init call:

  // instrumentation-client.ts
  Sentry.init({
    transportOptions: { fetchOptions: { credentials: 'same-origin' } },
  });

• nitro: Report a single http.server span per request

  A Nitro request now creates only one http.server span. The nested http.server spans with the origins auto.http.nitro.srvx and auto.http.nitro.h3 are removed. h3 route handlers now get a handler span, and middleware spans are direct children of the http.server span. If you have queries or alerts on the removed spans, change them to use the http.server span or the handler span.

• Use auto.http.http_server origin for all node:http server spans

  On Bun and Deno, node:http server spans now have the origin auto.http.http_server instead of auto.http.server, as on Node.js. On Node.js, nothing changes. Bun.serve spans keep auto.http.bun.serve and Deno.serve spans keep auto.http.deno. If you have ignoreSpans or beforeSendSpan rules, queries or alerts on auto.http.server, change them to use auto.http.http_server.

Other Changes

• browser: Add LoaderSentry type export

• cloudflare: Add isStreamingResponse option and detect streamed RSC responses

• core: Add dataCollection.mcp option

• core: Limit the body size of tunnel requests

• nextjs: Link use cache hits to their fill across instances

• nextjs: Wait for the resumed part of a document before starting the pageload

• nitro: Merge the nitro integrations into a single nitroIntegration

• server-utils: Emit execute_tool spans for Anthropic's beta.messages.toolRunner()

• astro: Defer to @sentry/cloudflare/vite on Cloudflare Workers

• aws-serverless: End the function.aws span when a callback-style handler calls back

• browser: Skip profiling for unsampled active root spans

• bundler-plugins: Check globalThis before global in the injected snippet

• bundler-plugins: Inject the release only into chunks that load at startup

• cloudflare: auto-instrument a re-exported default export

• cloudflare: Deliver check-ins and events from forked isolation scopes

• cloudflare: Don't hold Durable Object invocations open with the segment-end flush timer

• cloudflare: Keep default exports intact when auto-instrumenting

• core: Use trace_metric data category for metrics rate limits and client reports

• deno: Re-export portable helpers that Cloudflare exposes

• elysia: Set SDK metadata on the options passed to init

• elysia: Use Node transport on Node runtimes

• hono: Read connection info from the runtime instead of Hono helpers

• nextjs: Only inject applicationKey metadata into browser bundles

• nitro: Use forward slashes for resolved plugin paths on Windows

• node,vercel-edge,bundler-plugins: Ignore commit env vars set to their own name

• node: Guard user callbacks in the node:http server instrumentation

• node: Only read JavaScript and TypeScript source files in ContextLines

• node: Restore tsx runtime instrumentation

• nuxt: Delete Sentry-enabled source maps from Nitro output directories

• nuxt: Keep sourcesContent in Nuxt 5 server source maps

• react: Don't crash ErrorBoundary when error.cause is not an Error

• react: Match React Router navigations against root routes only

• server-runtime-injection: Load ESM hook without the build/esm package.json marker

• server-utils: Bundle the CommonJS dependencies of instrumented packages on Vite 8

• server-utils: Keep OpenAI decision confidence on Vercel AI decide spans

• server-utils: Nest LangChain run spans under their parent run

• server-utils: Stop the orchestrion Vite plugin from bundling the CJS build of @sentry/server-utils

• solidstart: Read server action route from the request's root span

• tanstackstart-react: Delete only the source maps that Sentry enabled

• vercel-edge: Expose portable tracing and feature flag helpers

Internal Changes

Work in this release was contributed by @4ktLuffy, @adityareddy-dev, @dasilvaluis, @faizansaiyed123, @jpdefo, @Jxxunnn, @mikamikasuki, @philipatkinson, @rubas, and @Shubham-Padkonde. Thank you for your contributions!

Bundle size

Important Changes

• bundler-plugins: Release @sentry/webpack-plugin, @sentry/vite-plugin, @sentry/rollup-plugin and @sentry/esbuild-plugin from the SDK repository

  The four standalone bundler plugins now release together with the SDK, so their version jumps from 5.4.1 to the SDK version. Each package re-exports the matching @sentry/bundler-plugins entry point, which we recommend for new projects. The plugin options do not change, but the update brings these breaking changes:

  • Node.js 20.19.0 or higher is required.

  • @sentry/webpack-plugin requires webpack 5.1 or higher. The @sentry/webpack-plugin/webpack5 entry point still works and exports the same plugin as @sentry/webpack-plugin.

  • The plugins use the sentry CLI SDK instead of @sentry/cli. Sentry self-hosted 26.4.2 or higher is supported. Lower versions may continue to work.

  • Deploys that the plugins create on Vercel use the value of VERCEL_TARGET_ENV (production, preview or a custom name) as their environment, instead of vercel-production or vercel-preview. To keep the old value, set release.deploy.env.

• server-utils: Instrument the OpenAI decisions API as gen_ai.decide spans

  OpenAI decisions.create calls now create gen_ai.decide spans.

Other Changes

• core: Support SuppressedError in LinkedErrors integration

• astro: Delete generated source maps for static output

• astro: Upload source maps of Astro 7's prerender build

• browser: Apply urlQueryParams to the Referer header

• cloudflare: auto-instrument when wrangler main is a package

• hono: Expose runtime-specific SDK options

• node: Instrument Prisma 8 CollectionBase from rc.15

• nuxt: Skip 3xx/4xx Nuxt errors in the vue:error hook

• server-utils: Read pi-durable 1.2.0 tool results from output

• server-utils: Transform modules once when two Sentry Vite plugins add orchestrion

• sveltekit: Add op and origin to Kit's sveltekit.endpoint span

• tanstackstart-react: Keep parametrized route names in Nitro 3 builds

• tanstackstart-react: Rewrite source paths of split route modules

Internal Changes

• license: Add cli FSL notice to package licenses

Work in this release was contributed by @kunal649 and @mketiku. Thank you for your contributions!

Bundle size

Important Changes

• cloudflare: Add opt-in cron monitoring for Cron Triggers

  The new cronTriggersIntegration sends check-ins for Cron Triggers. Each check-in includes the schedule from controller.cron, so Sentry creates the monitor on the first run. The integration is opt-in, because monitors are billed.

  Cron Triggers have no names, so map each cron expression of your wrangler config to a monitor slug. With the Sentry Cloudflare Vite plugin, add the integration to src/instrument.server.ts:

  // src/monitorSlugs.ts
  export const monitorSlugs: Record<string, string> = {
    '30 9 * * MON-FRI': 'daily-report',
  };
  
  // src/instrument.server.ts
  import * as Sentry from '@sentry/cloudflare';
  import { monitorSlugs } from './monitorSlugs';
  
  export default Sentry.defineCloudflareOptions(env => ({
    dsn: env.SENTRY_DSN,
    integrations: [Sentry.cronTriggersIntegration({ monitorSlug: cron => monitorSlugs[cron] })],
  }));
  
  // src/index.ts
  import { monitorSlugs } from './monitorSlugs';
  
  export default {
    async scheduled(controller, env) {
      switch (monitorSlugs[controller.cron]) {
        case 'daily-report':
          // Your daily report job
          break;
      }
    },
  };

  The monitorSlug function can also return monitor settings, for example { monitorSlug: 'daily-report', maxRuntime: 30 }, or undefined to send no check-ins for a trigger. Without monitorSlug, the SDK derives the slug from the cron expression. If you deploy with wrangler directly, pass the same integration to Sentry.withSentry.

• node: Add neonIntegration for @neondatabase/serverless (#25164, #25176)

  The new neonIntegration creates db spans for queries of the @neondatabase/serverless driver: for the WebSocket Client and Pool, and for the HTTP neon() function. This includes the neon-http and neon-serverless adapters of Drizzle. The integration is on by default when tracing is enabled.

• node: Stop sending the process session once request sessions are tracked

  Node servers sent release health data two times: as request session aggregates, and as the process session of processSessionIntegration. An error in a request also marked the process session as errored, so the SDK counted the error two times. Now the SDK drops the process session when it tracks the first request session. Scripts, CLIs and workers that do not serve requests keep the process session, and so do servers with httpServerIntegration({ sessions: false }). This changes the release health numbers of Node servers, because they no longer send the errored or crashed update of the process session.

• server-utils: Record decide calls as gen_ai.decide spans (#25270, #25272, #25274, #25281)

  Vercel AI experimental_decide calls, Mastra classifier evaluations, TypeSafe and LangChain Jev calls, and Workers AI calls to TypeSafe Jev and Cloudflare Clef models now create decide <model> spans with the op gen_ai.decide. Before, these spans had the op gen_ai.evaluate, which is now deprecated in the Sentry conventions. If you use gen_ai.evaluate in queries, alerts or dashboards, change it to gen_ai.decide.

• browser: Apply urlQueryParams to more URLs (#25262, #25289)

  The dataCollection.urlQueryParams option now also filters the query parameters of these URLs:

  • the page URL in event.request.url

  • the browser.* and resource.* span names with traceLifecycle: 'static'

  • the LCP URL attributes lcp.url and browser.web_vital.lcp.url

  • the URLs in fetch, XHR and navigation breadcrumbs

  • the ui.element.url attribute of elementTimingIntegration

  Before this fix, these URLs could send sensitive query values, for example ?jwt=..., to Sentry.

• nextjs: Apply top-level bundleSizeOptimizations to webpack and Turbopack builds

  The top-level bundleSizeOptimizations option now removes unused SDK code in webpack and in Turbopack builds. Before, the tree-shaking options had no effect on Turbopack. The webpack.treeshake option is deprecated. It still works, but when you set both options, bundleSizeOptimizations takes precedence.

Other Changes

• nuxt: Detect the server API with @nuxt/kit 4.6

• bundler-plugins: Escape JSON in generated injection code

• core: Don't mark http client spans as errors when the caller aborts

• core: Record span client report outcomes when discarding transactions

• core: Record client outcomes when beforeSend callbacks return invalid values

• core: Record span outcomes for spans dropped when building a transaction

• core: Report actual item count in client reports of envelope send failures

• core: Strip internal custom span name from streamed spans

• nextjs: Filter query parameters in request error context

• node: Don't mark fetch spans as errors when the caller aborts

• nuxt: Delete public source maps before Nitro lists its public assets

• nuxt: Keep @sentry/server-runtime-injection external on Nitro v3

• nuxt: Remove @opentelemetry/resources dev alias

• profiling-node: Stop the trace lifecycle profiler when spans are unsampled

• react-router: Respect custom default integrations

• remix: Respect custom default integrations

• server-utils: Avoid quadratic SQL summary regex backtracking

• server-utils: End Express layer spans when the client aborts

• server-utils: Record amqplib consumer info before the first delivery and instrument the callback API

• server-utils: Stop treating previous_response_id as the OpenAI conversation id

• sveltekit: Read load event pathname untracked

• sveltekit: Stop adapter-node 6 output dir probe from deleting the build

Internal Changes

Work in this release was contributed by @Philip-Nwabuwa and @4ktLuffy. Thank you for your contributions!

Bundle size

Important Changes

• nextjs: Add @sentry/nextjs/cloudflare

  The new @sentry/nextjs/cloudflare entry point exports withSentry for the Worker entry of a Next.js app on Cloudflare Workers, for example .open-next/worker.js of OpenNext. It is withSentry of @sentry/cloudflare with the Next.js server handling added, so a Next.js app on Workers gets the same spans as on Node.js.

  import * as Sentry from '@sentry/nextjs/cloudflare';
  import handler from './.open-next/worker.js';
  
  export default Sentry.withSentry(
    env => ({
      dsn: env.SENTRY_DSN,
      tracesSampleRate: 1.0,
    }),
    handler,
  );

• server-utils: Add instrumentation for pi-durable

  The new piDurableIntegration traces agents built with pi-durable: each run, with its model requests and tool calls.

• core: Correct sleep clock drift on telemetry timestamps

  When a device sleeps, the performance.now() clock of the browser stops. Before this change, timestamps of spans and other telemetry recorded after the sleep could be too early. The SDK now detects this drift and corrects its time origin, also for spans created from performance entries. Span end times are now computed from the performance.now() duration since the span start, like in OpenTelemetry (#24903).

Other Changes

• cloudflare: Skip spans for the pi_ tables of PiHarness

• remix: Propagate the server trace to Remix 3 page loads

• server-utils: Map Mastra classifier evaluations to gen_ai.evaluate spans

• server-utils: Record LangChain TypeSafeClassifier runs as gen_ai.evaluate spans

• browser: Check for clock drift on page lifecycle events

• core: Exclude attachments from internal exception events

• effect: Convert Effect span times to the Sentry clock

• effect: Detect HTTP spans named after the request method

• node: Register Vercel keep-alive listeners once

• replay: Place CLS and INP web vitals at the right time

• server-utils: Record LangGraph span I/O for non-MessagesAnnotation state

• sveltekit: Upload source maps with SvelteKit 3

Internal Changes

• cloudflare: Wrap vinext Worker entries with @sentry/nextjs/cloudflare

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

Bundle size

Important Changes

• core: Warn on repeated Sentry.init() and unbind the client on close()

  Sentry.init() now warns when it runs while a client is still active. For now, the new client still replaces the active client, but the active client is not closed, so state from both can mix. Call Sentry.init() once, or call await Sentry.close() before you call it again. Sentry.close() now unbinds the client it closes, so after close(), getClient() returns undefined, isInitialized() returns false, and a later init() sets up a new client. In @sentry/cloudflare, later requests no longer reuse the isolate's cached client once it is closed or closing. On the server, @sentry/nextjs and @sentry/remix now return the active client from a repeated init() call, not undefined.

Other Changes

• bun: Keep server spans open until streaming responses finish

• langchain: Derive gen_ai.conversation.id from the invoke config

• nextjs: Add code.file.path to use cache fill spans

• react-router: Export createSentryServerInstrumentation from the Cloudflare entry

• remix: Parameterize Remix 3 navigation spans

• remix: Parameterize Remix 3 page load spans

• remix: Report the matched route on Remix 3 HTML responses

• ai: Normalize token usage and preserve cache breakdowns

• browser-utils: Handle NS_ERROR_NOT_INITIALIZED from setTimeout in Firefox

• bun: Add conversationIdIntegration to the default integrations

• cloudflare: Detect TypeSafe Jev calls in Workers AI by model ID

• cloudflare: Keep an installed OpenTelemetry async context strategy

• feedback: Correct overlapping screenshot annotations and drag dimming

• nextjs: Don't capture forbidden() and unauthorized() as errors

• nextjs: Include basePath in request url of Pages Router errors

• nextjs: Skip init inside a request of @sentry/cloudflare

• node: Flush telemetry before Vercel functions are suspended

• nuxt: Do not inject debug IDs into the SSR build

• react-router: Pass the project when creating a release

• remix: Pass the project when creating a release

• server-utils: Derive the Vercel AI conversation id from the OpenAI conversation option

• server-utils: Instrument the Vercel AI experimental_decide channel event

• server-utils: Map Flue messages and token usage to the gen_ai conventions

• server-utils: Record Vercel AI experimental_telemetry.metadata on gen_ai spans

• sveltekit: Export consoleLoggingIntegration from worker entry

• tanstackstart-react: Fix server route parametrization gaps

• deprecated

  core: Deprecate SEMANTIC_ATTRIBUTE_SENTRY_ORIGIN

Internal Changes

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

Bundle size

Important Changes

• Remix 3 support (alpha, may break in minor releases)

  • feat(remix): Add Remix 3 browser SDK with a bundled client entry

  • feat(remix): Add source map upload for Remix 3

  • feat(remix): Capture Remix 3 component render errors

  • feat(remix): Complete Remix 3 server error handling

  • feat(remix): Inject debug IDs through the Remix 3 asset server

  • feat(remix): Run the orchestrion transform on Remix 3 browser modules

• nextjs: Add cache_origin span links to use cache hit spans

  A cache.get span for a "use cache" hit now carries a span link (sentry.link.type: 'cache_origin') to the cache.put span of the request that filled the cache entry, connecting the trace that reads a cached value to the trace that produced it.

• cloudflare: Don't treat DO constructor work as incoming RPC calls

  Durable Object constructors now run in their own isolation scope. When work that the constructor starts, for example a blockConcurrencyWhile callback, calls a method of the instance, that call is no longer treated as an incoming RPC call, so an error the instance catches itself is no longer reported as unhandled. As a result, Sentry.setTag(), setUser() and setContext() in a constructor now apply only to that constructor work. They no longer reach later fetch, RPC or alarm invocations, because the scope they used to write to is shared by every Durable Object and handler in the isolate. Use initialScope for static data, and set per-instance data in each handler.

• breaking

  effect: Change peerDependency to v4 and fix currentSpan

  @sentry/effect now requires a stable Effect v4 release. Effect v4 beta and release candidate versions are no longer supported. @sentry/effect is in alpha, so this ships in a minor release.

Other Changes

• astro: Register astro route provider

• cloudflare: Trace TypeSafe Jev calls in Workers AI as evaluate spans

• core: Add route provider API for parameterized route resolution

• effect: Add opt-in for external span parents and isolate root spans

• nextjs: Register nextjs route provider

• nuxt: Register nuxt route provider

• remix: Register remix route provider

• vue: Register Vue route provider

• bundler-plugins: Keep debug IDs on Vite source maps after the preload rewrite

• bundler-plugins: Stabilize debug IDs for Rolldown and Vite 8 builds

• cloudflare: Skip binding instrumentation work when spans are not sent

• core, node, bun, deno: Align server span client address with event IP

• hono: Return the existing client on repeated init in Bun and Deno

• nitro: Capture errors only through the Nitro error hook

• profiling-node: Send profile chunks with client.sendEnvelope

• react-router: Avoid duplicating Vite config arrays

• react-router: Resolve the Cloudflare entry in Workers and skip trace meta tags in prerendered pages

• server-utils: Match the Anthropic stream helper header regardless of case

• server-utils: Skip Fastify 4xx errors raised before the reply status is set

• tanstackstart-react: Avoid duplicating Vite config arrays

Internal Changes

• license: Add cli FSL notice

Work in this release was contributed by @Shubham-Padkonde and @tobias-schnabel. Thank you for your contributions!

Bundle size

Important Changes

• hono: Add orchestrion-based auto-instrumentation

  Hono is now instrumented automatically. Request spans are named after the matched Hono route, each middleware gets its own span, and errors thrown in handlers are captured.

• node/bun: Enable dedupeIntegration by default

  @sentry/node and @sentry/bun now include dedupeIntegration in their default integrations, like the browser, Deno, Vercel Edge and Cloudflare SDKs. When the same error is captured two times in a row, only the first event is sent. To keep the previous behavior, remove the integration: integrations: defaults => defaults.filter(integration => integration.name !== 'Dedupe').

• remix: Instrument Remix 3 server requests via fetch-router

  On Remix 3, the SDK now adds the matched route as http.route, the response status and a low-cardinality name to the http.server span of each fetch-router request. Start the app with --import @sentry/remix/v3/node in place of --import remix/node-tsx.

Other Changes

• elysia: Export bunRuntimeMetricsIntegration

• react-router: Support request-scoped CSP nonces in createSentryHandleRequest

• aws-serverless: Keep Lambda extension polling past 300s

• browser-utils: Stop leaking DOM instrumentation listeners on mismatched removals

• core: Resolve escape sequences in fmt / parameterize messages

• deno: Flush buffered metrics and logs before process exit

• node: End Express layer spans when next is called

• node: Flush buffered metrics on process exit

• nuxt: Fix CommonJS interop for force-inlined instrumented packages

• server-utils: Preserve raw Anthropic response bodies

• server-utils: Preserve raw Groq and Together response bodies

• server-utils: Preserve raw OpenAI embeddings and conversation responses

• server-utils: Preserve response bodies for OpenAI parse helpers

• solidstart: Support rolldownOptions in instrumentation file plugin

• sveltekit: Skip trace meta tags when prerendering

• vue: Share one root render span debounce timer across components

• server-utils: Avoid quadratic SQL sanitizer output handling

Internal Changes

Work in this release was contributed by @nabi-noor, @LuccaRebelloToledo, @andasan, @breken-ai, @EmileBrunelle, and @diobriggs. Thank you for your contributions!

Bundle size

Important Changes

• server-utils: Auto-instrument MCP servers via orchestrion

  A new default mcpServerIntegration wraps every McpServer instance (from @modelcontextprotocol/server and @modelcontextprotocol/sdk) when it is created. You no longer need to call wrapMcpServerWithSentry manually. You can still call wrapMcpServerWithSentry to override options, for example recordInputs: false.

• node: Support Prisma 8 in prismaIntegration

  prismaIntegration now creates a prisma:client:operation span for each Prisma 8 ORM call, with the database query spans nested below it. No code changes are necessary.

• server-utils: Add TypeSafe integration

  A new default typesafeIntegration creates a gen_ai.evaluate span for each TypeSafe Jev call through @typesafe-ai/sdk (TypeSafeClient.systemOne). For runtimes without auto-instrumentation, use instrumentTypeSafeClient().

• server-utils: Instrument Vercel AI experimental_evaluate

  Vercel AI experimental_evaluate calls now create a gen_ai.evaluate span, with the state and questions as input messages and the answers as output messages.

Other Changes

• browser: Add onError callback to showReportDialog

• bun: Add client address, port and protocol to Bun.serve spans

• cloudflare: Re-export httpServerIntegration from /request

• remix: Add Remix 3 export subpaths and optional peer deps

• server-utils: Support amqplib v2

• server-utils: Support tedious v20

• Injection silently no-ops on Windows (registerHooks path)

• bun: Keep diagnostics channel subscriptions alive

• cloudflare: Call connect() on the binding for service bindings and DO stubs

• cloudflare: Keep the user's class name when auto-wrapping an export

• core: Support joined set-cookie headers (split them)

• nextjs: Don't prepend basePath to absolute router navigation URLs

• nextjs: Limit Turbopack orchestrion loader to instrumented packages

• nextjs: Stop Turbopack loaders from loading the Sentry CLI

• server-runtime-injection: Keep ES modules working on Deno

• server-utils: Deduplicate Google GenAI streaming tool calls

• sveltekit,remix: Export Mistral manual wrapper

• sveltekit: Resolve @opentelemetry/api via the SDK on SvelteKit 3

• wasm: Map wasm:// stack frames to registered debug images

• bundler-plugins: Use fast component annotation for HTML injection mode

• bundler-plugins: Use fast component annotation for Webpack and Turbopack

Internal Changes

• server-utils: Use Bun-safe diagnostics channel wrappers in MCP integration

Work in this release was contributed by @camc314, @ihsraham, @zkasuran, @Shubham-Padkonde, and @itz-puneet. Thank you for your contributions!

Bundle size

@sentry/ember

• breaking

  angular,ember,sveltekit: Use router span op for frontend routers

• breaking

  ember: Update to v2 addon format

• breaking

  ember: Use function and ui.task span ops for route hooks and runloop

• breaking

  ember: Change 'ui.ember.component.render' to ui.render

• v10/deno: Re-export portable helpers that Cloudflare exposes

• v10/core: Drop sampled-out errors before they take a promise buffer slot

• v10/core: Stop sending client reports for breadcrumbs

• v10/core: Use trace_metric data category for metrics rate limits and client reports

• v10/nextjs: Don't crash Cloudflare workers on import of the Next.js version helper

Bundle size

Important Changes

• v10/nextjs: Add a tunnel route handler that sends only the event payload to Sentry

  The tunnelRoute option can now send events through a route handler in your app. The handler forwards only the event payload to Sentry, and no request headers. To use it, add this file next to your tunnelRoute option:

  // app/sentry-tunnel/route.ts (or src/app/sentry-tunnel/route.ts)
  export { POST } from '@sentry/nextjs/tunnel';

  The handler accepts events for the DSN of your server SDK. To accept other DSNs, use createSentryTunnelRoute({ allowedDsns }) from the same import. Without the file, the tunnel route works as before.

  With the handler, tunnel requests go through your middleware. If your middleware blocks unauthenticated requests, exclude the tunnel route in its matcher.

  Also, the server no longer sends spans of tunnel requests when span streaming is on, because these spans only show the SDK's own traffic.

• v10/nextjs: Send tunnel route requests with credentials: 'omit'

  With tunnelRoute and no tunnel route handler, @sentry/nextjs now sends events from the browser with credentials: 'omit', because the tunnel route does not need cookies.
  If a layer in front of your app checks cookies before it lets requests through (for example Vercel Deployment Protection), you can send them again in your browser Sentry.init call:

  // instrumentation-client.ts
  Sentry.init({
    transportOptions: { fetchOptions: { credentials: 'same-origin' } },
  });

• breaking

  v10/deps: Limit @opentelemetry/api to <1.10.0 and the OpenTelemetry SDK to <3.0.0

  Breaking change

  If your app uses @opentelemetry/api 1.10.0 or OpenTelemetry SDK v3 together with v10 of the Sentry SDK, you must stay on @opentelemetry/api below 1.10.0 and OpenTelemetry SDK v2, or upgrade to v11.

  @opentelemetry/api 1.10.0 only works with OpenTelemetry SDK v3 (@opentelemetry/core 3.x, @opentelemetry/instrumentation 0.300.x). The SDK v2 packages that v10 uses only support @opentelemetry/api below 1.10.0, and SDK v3 needs Node.js 22.15.0 or newer, while v10 supports Node.js 18 and newer. For this reason, v10 now limits @opentelemetry/api to <1.10.0, and the @opentelemetry/instrumentation and @opentelemetry/exporter-trace-otlp-http peer dependencies of @sentry/node-core to <0.300.0.

  If your app depends on @opentelemetry/api directly, use a version below 1.10.0 (for example ~1.9.1). With 1.10.0, your app and the Sentry SDK use different copies of the API, and the OpenTelemetry calls of your app do not see the tracer provider of the Sentry SDK.

  To use @opentelemetry/api 1.10.0 and OpenTelemetry SDK v3, upgrade to v11 of the Sentry SDK. For the upgrade steps, see the migration guide.

Other Changes

• v10/core: Limit the body size of tunnel requests

• v10/astro: Upload source maps of Astro 7's prerender build

• v10/aws-serverless: End the function.aws span when a callback-style handler calls back

• v10/browser: Apply urlQueryParams to event URLs, static span names and LCP URLs

• v10/browser: Apply urlQueryParams to the Referer header

• v10/browser: Skip profiling for unsampled active root spans

• v10/build: Make CJS re-exports visible to Node ESM imports

• v10/bundler-plugins: Check globalThis before global in the injected snippet

• v10/bundler-plugins: Escape JSON in generated injection code

• v10/bundler-plugins: Inject the release only into chunks that load at startup

• v10/cloudflare: auto-instrument a re-exported default export

• v10/cloudflare: auto-instrument when wrangler main is a package

• v10/cloudflare: Bind a default re-export with var in the Vite transform

• v10/cloudflare: Keep default exports intact when auto-instrumenting

• v10/core: Don't mark http client spans as errors when the caller aborts

• v10/core: Record span outcomes for spans dropped when building a transaction

• v10/core: Stop treating previous_response_id as the OpenAI conversation id

• v10/hono: Expose runtime-specific SDK options

• v10/nextjs: Apply top-level bundleSizeOptimizations to webpack and Turbopack builds

• v10/nextjs: Filter query parameters in request error context

• v10/nextjs: Only inject applicationKey metadata into browser bundles

• v10/nitro: Use forward slashes for resolved plugin paths on Windows

• v10/node: Don't mark fetch spans as errors when the caller aborts

• v10/node: Only read JavaScript and TypeScript source files in ContextLines

• v10/node: Read module versions from the isolated layouts of pnpm and Bun

• v10/nuxt: Delete public source maps before Nitro lists its public assets

• v10/nuxt: Keep sourcesContent in Nuxt 5 server source maps

• v10/nuxt: Skip 3xx/4xx Nuxt errors in the vue:error hook

• v10/react: Don't crash ErrorBoundary when error.cause is not an Error

• v10/react: Match React Router navigations against root routes only

• v10/react-router: Respect custom default integrations

• v10/remix: Respect custom default integrations

• v10/replay: Apply attribute masking to breadcrumb messages

• v10/server-utils: Avoid quadratic SQL summary regex backtracking

• v10/server-utils: End Express layer spans when the client aborts

• v10/sveltekit: Add op and origin to Kit's sveltekit.endpoint span

• v10/tanstackstart-react: Keep parametrized route names in Nitro 3 builds

• v10/tanstackstart-react: Rewrite source paths of split route modules

Internal Changes

Bundle size

• v10/deps: Bump bundler plugins to 5.4.1

• v10/ai: Normalize token usage and preserve cache breakdowns

• v10/core: Exclude attachments from internal exception events

• v10/effect: Detect HTTP spans named after the request method

• v10/sveltekit: Upload source maps with SvelteKit 3

Bundle size

• v10/browser-utils: Handle NS_ERROR_NOT_INITIALIZED from setTimeout in Firefox

• v10/feedback: Correct overlapping screenshot annotations and drag dimming

• v10/nextjs: Include basePath in request url of Pages Router errors

• v10/nuxt: Do not inject debug IDs into the SSR build

• v10/sveltekit: Export consoleLoggingIntegration from worker entry

• v10/sveltekit: Resolve @opentelemetry/api via the SDK on SvelteKit 3

• v10/vue: Share one root render span debounce timer across components

Internal Changes

Bundle size

• v10/vue,nuxt: Record default UI spans without Options API (mixins)

• v10/aws-serverless: Keep Lambda extension polling past 300s

• v10/deno: Flush buffered metrics and logs before process exit

• v10/nitro: Capture errors only through the Nitro error hook

• v10/node-core: Flush buffered metrics on process exit

• v10/react-router: Avoid duplicating Vite config arrays

• v10/tanstackstart-react: Avoid duplicating Vite config arrays

Internal Changes

Bundle size

• v10/tanstackstart-react: Reject non-POST requests to the managed tunnel route

Internal Changes

Bundle size

• v10/cloudflare: Enforce flush timeout across Workflow lifecycle

• v10/core: Apply dataCollection.urlQueryParams to collected URLs and query strings

• v10/nextjs: Align tunnel request matching in middleware with tunnel rewrite

• v10/node: Stop leaking unhandled rejections on aborted Vercel AI streams

Bundle size

• v10/cloudflare: Capture telemetry from untraced Durable Object RPC calls

• v10/cloudflare: Instrument namespaces returned by jurisdiction()

• v10/hono: Allow @cloudflare/workers-types v5 as peer dependency

• v10/nextjs: Resolve Next.js version relative to the SDK when cwd differs

Bundle size

Important Changes

• v10/effect: Capture errors through the Effect v4 ErrorReporter API

  On Effect v4, Sentry.effectLayer now registers a Sentry ErrorReporter. Failures that pass through Effect.withErrorReporting, ErrorReporter.report or the built-in HTTP and RPC reporting boundaries are captured automatically, with ErrorReporter.ignore, ErrorReporter.severity and ErrorReporter.attributes annotations respected. Nothing changes on Effect v3.

Other Changes

• v10/core: Accept a CollectBehavior shorthand for dataCollection.httpHeaders

• v10/browser: Release the XHR virtualError once the request completed

• v10/browser-utils: Skip nullish LCP entries in vendored web-vitals

• v10/bundler-plugins: Stamp debug IDs onto emitted source maps when disable-upload is set

• v10/core: Don't instrument the SDK's own envelope requests

• v10/nextjs: Only include emitted chunk directories in Turbopack sourcemap upload

• v10/nitro: Import from nitro/h3 instead of h3 directly

• v10/node-core: Don't recurse in logAndExitProcess on a broken stdio pipe

• v10/nuxt: Detect Nitro version via the app's Nuxt dependency chain

• v10/replay: Don't rewrite already-emitted nodes when syncing mirror attributes

Bundle size

• v10: Streamline isolation scope handling & reset in isolation scopes

• server-utils: Include Gemini reasoning tokens in Vercel AI token usage

• v10/browser: Set user_agent.original on all spans for consistent filtering

• v10/cloudflare: Auto-instrument classes re-exported from the worker entry

• v10/core: Guard loadModule default parameter against ESM scope

• v10/core: Match wrapped Facebook Mobile browser errors in DEFAULT_IGNORE_ERRORS

• v10/core: Resolve MCP capture policy per operation

• v10/nextjs: Fix SDK import crashing under jsdom/happy-dom

• v10/nextjs: Keep the Pages Router runtime out of App Router client bundles

• v10/nextjs: Register Vercel AI span processors on Next.js

• v10/nuxt: Windows file:// for import-in-the-middle hook and isAbsolute for C:\

• v10/sveltekit: Handle SvelteKit 3 error kinds in handleErrorWithSentry

• v10/sveltekit: Read Cloudflare execution context from platform.ctx

• v10/sveltekit: Read SvelteKit config from the Vite plugin

Internal Changes

Work in this release was contributed by @halillusion and @zkasuran. Thank you for your contributions!

Bundle size

Important Changes

• v10/nextjs: Add @sentry/nextjs/config entry point

  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

• deprecated

  v10/node: Deprecate shouldHandleError on setupExpressErrorHandler and setupFasitfyErrorHandler

• v10/cloudflare: Instrument Durable Object handlers installed as read-only properties

Internal Changes

Bundle size

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.

• 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 this worker (its own Durable Objects and self service bindings) are derived from your wrangler config and added for you.

Other Changes

• v10/astro: Support astro v7 route patterns properly

• v10/bundler-plugins: Preserve full file path in component annotation source maps

• v10/core: Store child span timeout handle in _childSpanTimeoutID

• v10/node: Only end the process session when it is still ok

• v10/react-router: Use react-router's own instrumentation types instead of a mirrored copy

• v10/replay: Suppress Worker destroyed error on session expiry

• v10/server-utils: Keep orchestrion registration out of tree-shaking

• v10/server-utils: Stop shipping orchestrion bundler plugins as production dependencies

• v10/server-utils: Support openai v7 in auto-instrumentation

• v10/sveltekit: Detect native tracing in flattened SvelteKit 3 config

Internal Changes

Work in this release was contributed by @ryanrho-mercor, @lux-in-tenebris-lucet, and @suhailopensource. Thank you for your contributions!

Bundle size

Important Changes

• breaking

  v10/core: Enable logs by default

The enableLogs client option now defaults to true, so Sentry Logs work without any manual opt-in. Nothing is captured unless you call the Sentry.logger.* APIs or add a log-forwarding integration (such as consoleLoggingIntegration, pinoIntegration, or the winston transport), and you can set enableLogs: false to opt out. Although a default change like this would normally land in a major release, we are shipping it in a minor after careful consideration, since it sends no data on its own and only takes effect once you actively use the logging APIs or a logging integration.

Other Changes

• deprecated

  v10/core: Deprecate scope.clear() method

• v10/core: Bound child span tracking on long-lived spans

• v10/core: Read Supabase PostgREST headers from Headers instances

• v10/hono: Use captureException from scope, not from Client

• v10/nuxt: Delete source maps after Nitro finishes building

• v10/react-router: Carry multi-byte UTF-8 across SSR stream chunk boundaries

• v10/react: Match TanStack Router pageload against the router location

Internal Changes

Bundle size

• v10/core: Support stable MCP SDK v2

• v10/solid,solidstart: Support @solidjs/router v1

• v10/cloudflare: Fork the isolation scope for Durable Object methods

• v10/cloudflare: Get original waituntil in workflows

• v10/cloudflare: Instrument DO RPC methods on the prototype, not a Proxy

• v10/cloudflare: Set agent conversation id on the onRequest path

• v10/cloudflare: Set conversation id independent of session name

• v10/cloudflare: Try/catch on non-configurable prototypes

• v10/cloudflare: Use gen_ai.agent.name for class names

• v10/core,browser: Handle errors from other realms

• v10/core: Sample errors after beforeSend while preserving session updates

• v10/hono: Include originalException in captured exception hint

• v10/nextjs: meriyah issue for standalone build

• v10/nextjs: Remove tracing from middleware wrappers

• v10/profiling-node: Respect profileSessionSampleRate in trace profile lifecycle

• v10/react-router: Preserve sourcemaps.disable when unstable_sentryVitePluginOptions is set

• v10/react: Remove routes from shared set on <Routes> unmount

• v10/sveltekit: Export metrics from worker entry point

Internal Changes

Work in this release was contributed by @davidmurdoch, @Jxxunnn, and @kamilogorek. Thank you for your contributions!

Bundle size