@sentry/core
11.11.0 · 5 Nov 2026MIT101.6M / weekRepositoryHomepagenpmAtom feed
Where each line stands
Plan an upgrade- 11.x11.11.0No known advisoryLatest line
- 10.x10.78.0No known advisoryTo 11.11.0
- 9.x9.47.2No known advisoryTo 11.11.0
- 8.x8.55.2No known advisoryTo 11.11.0
- 7.x7.120.4No known advisoryTo 11.11.0
- 6.x6.19.7No known advisoryTo 11.11.0
Latest releases
All 581 releases- 11.x · latest line
11.11.0
5 Nov 2026- Deprecated
core: Deprecate the released
handleTunnelRequestform and reword theserveTunnelIntegrationdocs nestjs: Add an option to monitor every @Cron method
Set
monitorCronJobs: trueonnestIntegration()to send check-ins for every@Cron()method, without adding@SentryCronto each one. It's off by default. Each monitored job creates a monitor in Sentry, and monitors are billed. UseexcludeCronJobsto skip jobs by slug. Methods that also have@SentryCroncheck in once, with the slug and options passed to@SentryCron.node: Add cronJobIntegration to monitor cron jobs
Add
Sentry.cronJobIntegration()tointegrationsto send check-ins for every namedCronJobof thecronpackage (4.3+), with the job name as the monitor slug. It's off by default. Each monitored job creates a monitor in Sentry, and monitors are billed. UseexcludeJobsto skip jobs by name.Sentry.cron.instrumentCronis deprecated; usecronJobIntegrationinstead.
Important Changes
nestjs: Add an option to monitor every @Cron method
Set
monitorCronJobs: trueonnestIntegration()to send check-ins for every@Cron()method, without adding@SentryCronto each one. It's off by default. Each monitored job creates a monitor in Sentry, and monitors are billed. UseexcludeCronJobsto skip jobs by slug. Methods that also have@SentryCroncheck in once, with the slug and options passed to@SentryCron.node: Add cronJobIntegration to monitor cron jobs
Add
Sentry.cronJobIntegration()tointegrationsto send check-ins for every namedCronJobof thecronpackage (4.3+), with the job name as the monitor slug. It's off by default. Each monitored job creates a monitor in Sentry, and monitors are billed. UseexcludeJobsto skip jobs by name.Sentry.cron.instrumentCronis deprecated; usecronJobIntegrationinstead.server-utils: Instrument @anthropic-ai/sdk 1.x and turn off its own OTel spans
The Anthropic integration now instruments
@anthropic-ai/sdk1.x. Since 0.134 the SDK also records its own OpenTelemetry spans, such asanthropic.messages.create, which duplicated Sentry'sgen_aispans. Once Sentry instruments the SDK, it setsANTHROPIC_OPEN_TELEMETRY=falseto turn those spans off. To keep them, setANTHROPIC_OPEN_TELEMETRY=trueor pass theopenTelemetryoption to the Anthropic client.nextjs: Mark pageloads of cached pages
When Next.js serves a page from its cache, for example an ISR page or a
cacheComponentsshell, the pageload now has thepage.server_rendering.typeattribute. It isstaticif the whole page came from the cache, andpartially_staticif parts of it rendered for this request. Then the pageload stays connected to this request, as before. If the request that rendered the cached page was sampled, the pageload also links to it. So in Sentry, a cached page no longer looks like missing server instrumentation.
Other Changes
astro: Add
@sentry/astro/integrationentry for the Astro integrationbundler-plugins: Add
sourcemaps.deleteSourcemapsAfterUploadand staged uploadsnestjs: Derive SentryCron monitor config from @Cron
nextjs: Add
applicationKeyExcludeDependenciesoptionnode: Add
awsLambdaWebIntegrationfor Lambda Web Functionsnode: Add BullMQ integration
node: Add nodeCronIntegration to monitor node-cron tasks
node: Add nodeScheduleIntegration to monitor node-schedule jobs
node: Support postgres v4 through its native tracing channels
server-utils: Extract
getSqlSpanNamefor SQL span namesserver-utils: Move to new
getSqlQueryAttributeshelper for consistencyserver-utils: Record AI SDK v7 runtime and tool context on Vercel AI spans
server-utils: Set
db.operation.nameon SQL spansserver-utils: Support @mistralai/mistralai v3
solidstart: Export
withSentryfrom@sentry/solidstart/viteastro: Initialize the server SDK on the first endpoint request
browser: Attribute long animation frame spans to the longest script
bundler-plugins: Inject debug IDs into every esbuild rebuild
bundler-plugins: Upload literal artifact paths
cloudflare: Run build-time instrumentation in vite dev
core: Call native toString without page-replaceable lookups in FunctionToString
core: Enforce linked error limits for aggregate and suppressed errors
core: Only create Supabase db spans when there is a parent span
core: Preserve span links through beforeSendSpan
core: Respect header collection for session user agents
nextjs: Don't abort Cache Components renders on Cloudflare Workers when requests overlap
nextjs: Drop tunnel requests under the Next.request proxy root span
nextjs: Fork isolation scope for Next.request proxy root spans
nextjs: Strip source map comments before trailing debug IDs
nitro: Capture errors thrown in tasks
nuxt: Keep storage instrumentation plugin synchronous
replay: Skip buffered replays for captureMessage stacks from the attachStacktrace default
server-utils: Fix orchestrion source maps of instrumented modules
server-utils: Read the pi-durable session id in every phase outside a run
server-utils: Require a parent span for Firestore operations
server-utils: Require a parent span for Tedious queries
server-utils: Use onlyIfParent for Firestore spans
server-utils: Use onlyIfParent for Tedious spans
solidstart: Serve the managed tunnel under Vite's base on SolidStart 2
sveltekit: Resolve Handle and ResolveOptions types on SvelteKit 3
wasm: Skip length prefix in 16-byte build IDs
- Deprecated
core: Deprecate the released
handleTunnelRequestform and reword theserveTunnelIntegrationdocs
Internal Changes
build: Handle CRLF line endings in pnpm-workspace.yaml check
Work in this release was contributed by @lazerg, @chiliec, @61465, @jpdefo, and @AyeshaWaseemAhmad. Thank you for your contributions!
Bundle size
Path Size @sentry/browser 29.69 KB @sentry/browser - with treeshaking flags 27.87 KB @sentry/browser - with treeshaking flags tracing without tracing 27.77 KB @sentry/browser (incl. Tracing) 51.49 KB @sentry/browser (incl. Tracing + Span Streaming) 51.5 KB @sentry/browser (incl. Tracing, Profiling) 54.4 KB @sentry/browser (incl. Tracing, Replay) 90.85 KB @sentry/browser (incl. Tracing, Replay) - with treeshaking flags 79.71 KB @sentry/browser (incl. Tracing, Replay with Canvas) 95.49 KB @sentry/browser (incl. Tracing, Replay, Feedback) 108.17 KB @sentry/browser (incl. Feedback) 46.86 KB @sentry/browser (incl. sendFeedback) 34.67 KB @sentry/browser (incl. FeedbackAsync) 39.66 KB @sentry/browser (incl. Metrics) 30.7 KB @sentry/browser (incl. Logs) 30.99 KB @sentry/browser (incl. Metrics & Logs) 31.69 KB @sentry/react 31.53 KB @sentry/react (incl. Tracing) 53.81 KB @sentry/vue 37.77 KB @sentry/vue (incl. Tracing) 54.44 KB @sentry/svelte 29.71 KB @sentry/remix (Remix 3 client bundle) 56.46 KB CDN Bundle 31.44 KB CDN Bundle (incl. Tracing) 52.01 KB CDN Bundle (incl. Logs, Metrics) 33.66 KB CDN Bundle (incl. Tracing, Logs, Metrics) 53.91 KB CDN Bundle (incl. Replay, Logs, Metrics) 74.1 KB CDN Bundle (incl. Tracing, Replay) 89.33 KB CDN Bundle (incl. Tracing, Replay, Logs, Metrics) 91.21 KB CDN Bundle (incl. Tracing, Replay, Feedback) 95.29 KB CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) 97.24 KB CDN Bundle - uncompressed 92.45 KB CDN Bundle (incl. Tracing) - uncompressed 153.97 KB CDN Bundle (incl. Logs, Metrics) - uncompressed 98.77 KB CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed 159.58 KB CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed 227.25 KB CDN Bundle (incl. Tracing, Replay) - uncompressed 272.81 KB CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed 278.4 KB CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 286.2 KB CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed 291.77 KB @sentry/nextjs (client) 56.69 KB @sentry/sveltekit (client) 52 KB @sentry/core/server 43.21 KB @sentry/core/browser 13.6 KB @sentry/node 152.29 KB @sentry/node/import (ESM hook with diagnostics-channel injection) 80.35 KB @sentry/node - without tracing 94.62 KB @sentry/node - without channel injection 133.08 KB @sentry/aws-serverless 102.63 KB @sentry/cloudflare (withSentry) - minified 195.97 KB @sentry/cloudflare (withSentry) 487.35 KB @sentry/nextjs/cloudflare (withSentry) - minified 217.46 KB 11.10.0
28 Oct 2026Add a managed tunnel that the SDK derives from the DSN (#25199, #25200, #25783)
Set
tunnel: truein your browserSentry.initcall 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 exporthandleTunnelRequestIfMatched,handleTunnelRequest,isTunnelRequestandgetTunnelPath:app.use((req, res, next) => Sentry.handleTunnelRequestIfMatched(req, res) ?? next());
The
requestoption ofhandleTunnelRequestis deprecated and will be removed in v12.Make span origins spec compliant
Some span origins changed their names to follow the trace origin spec:
If you have
ignoreSpansrules, queries or alerts on the old origins, change them to use the new origins.bun: Add incoming request options and request sessions to
bunServerIntegrationbunServerIntegrationnow accepts the same options asdenoServeIntegration:ignoreRequestBody,ignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreated,onSpanEnd,sessionsandsessionFlushingDelayMS. The callbacks receive the webRequest.Bun.servenow records a request session for each incoming request. Sessions are sent only when areleaseis set. To turn them off, setbunServerIntegration({ sessions: false }).ignoreStaticAssetsdefaults totrue, soBun.serveno longer creates spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, setbunServerIntegration({ ignoreStaticAssets: false }).Bun.servespans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled. Errors thrown forOPTIONSandHEADrequests are now captured.
Important Changes
Add a managed tunnel that the SDK derives from the DSN (#25199, #25200, #25783)
Set
tunnel: truein your browserSentry.initcall 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 exporthandleTunnelRequestIfMatched,handleTunnelRequest,isTunnelRequestandgetTunnelPath:app.use((req, res, next) => Sentry.handleTunnelRequestIfMatched(req, res) ?? next());
The
requestoption ofhandleTunnelRequestis 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 nowauto.queue.amqplib.*, andauto.kafkajs.*is nowauto.queue.kafkajs.*.auto.vercelai.channelis nowauto.ai.vercelai.auto.firebase.firestoreis nowauto.db.firebase.firestore, andauto.firebase.functionsis nowauto.function.firebase.auto.aws.aws_sdkis nowauto.{rpc,db,queue,ai}.aws_sdk, with the category from the span op.auto.aws_lambdais nowauto.function.aws_serverless.auto.mcp.notificationis nowauto.function.mcp_server.notification.auto.db.cloudflare.durable_object.sqlis nowauto.db.cloudflare.durable_object_sql.auto.http.browser.{lcp,cls,inp}is nowauto.ui.browser.{lcp,cls,inp}.
If you have
ignoreSpansrules, queries or alerts on the old origins, change them to use the new origins.bun: Add incoming request options and request sessions to
bunServerIntegrationbunServerIntegrationnow accepts the same options asdenoServeIntegration:ignoreRequestBody,ignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreated,onSpanEnd,sessionsandsessionFlushingDelayMS. The callbacks receive the webRequest.Bun.servenow records a request session for each incoming request. Sessions are sent only when areleaseis set. To turn them off, setbunServerIntegration({ sessions: false }).ignoreStaticAssetsdefaults totrue, soBun.serveno longer creates spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, setbunServerIntegration({ ignoreStaticAssets: false }).Bun.servespans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled. Errors thrown forOPTIONSandHEADrequests are now captured.bun: Inject debug IDs and upload source maps in
sentryBunPluginsentryBunPluginfrom@sentry/bun/pluginnow accepts the same options assentryEsbuildPlugin(org,project,authToken,release,sourcemaps, ...). WhenBun.buildwrites source maps tooutdir, 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 runsentry sourcemap injectandsentry sourcemap uploadafter the build.Like the other bundler plugins,
sentryBunPluginnow sends build telemetry and injects the release it detects (for example, from git). To turn off telemetry, settelemetry: false.cloudflare: Add incoming request span options to
httpServerIntegrationCloudflare's
httpServerIntegrationnow acceptsignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreatedandonSpanEnd, with the same meaning as in the Node, Deno and Bun integrations. The callbacks receive the webRequest.ignoreStaticAssetsdefaults totrue, so workers no longer create spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, sethttpServerIntegration({ ignoreStaticAssets: false }). Request spans also follow the client's tracing configuration by default, so the SDK does not start them when tracing is disabled. IfignoreRequestBodythrows, the request no longer fails, and the SDK skips the body.cloudflare: Let users configure the channel integrations
When the
@sentry/cloudflare/viteplugin bundles an instrumented package (for examplepgoropenai), the SDK adds the matching integration with its default options.@sentry/cloudflarenow exports these integrations, so you can set their options, for example ininstrument.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: truethe SDK logs a warning.node: Add
onSpanEndtohttpIntegrationhttpIntegrationandhttpServerSpansIntegrationnow acceptonSpanEnd, 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/coreand@sentry/server-utilswhere they work on that runtime:Node and Bun now export
moduleMetadataIntegration,instrumentPostgresJsSql,instrumentCreateReactAgent,awsIntegrationand theFlueOptionstype.awsIntegrationwas already in their default integrations.Deno and Cloudflare now export
parameterizeandinstrumentStateGraphCompile.Bun and Cloudflare now export the
LogandLogSeverityLeveltypes.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' }). Yoursentry.server.configloads 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_toolspans for Anthropic'sbeta.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
varin the Vite transformcloudflare: Do not add back channel integrations the user removed
cloudflare: Skip comments when locating the
defaultkeyword in the Vite transformcore: 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
undicifetch andnode:httpnode: 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
Path Size @sentry/browser 29.63 KB @sentry/browser - with treeshaking flags 27.79 KB @sentry/browser - with treeshaking flags tracing without tracing 27.69 KB @sentry/browser (incl. Tracing) 51.37 KB @sentry/browser (incl. Tracing + Span Streaming) 51.38 KB @sentry/browser (incl. Tracing, Profiling) 54.24 KB @sentry/browser (incl. Tracing, Replay) 90.64 KB @sentry/browser (incl. Tracing, Replay) - with treeshaking flags 79.52 KB @sentry/browser (incl. Tracing, Replay with Canvas) 95.25 KB @sentry/browser (incl. Tracing, Replay, Feedback) 107.93 KB @sentry/browser (incl. Feedback) 46.77 KB @sentry/browser (incl. sendFeedback) 34.59 KB @sentry/browser (incl. FeedbackAsync) 39.57 KB @sentry/browser (incl. Metrics) 30.61 KB @sentry/browser (incl. Logs) 30.89 KB @sentry/browser (incl. Metrics & Logs) 31.55 KB @sentry/react 31.4 KB @sentry/react (incl. Tracing) 53.61 KB @sentry/vue 37.7 KB @sentry/vue (incl. Tracing) 54.2 KB @sentry/svelte 29.66 KB @sentry/remix (Remix 3 client bundle) 56.3 KB CDN Bundle 31.32 KB CDN Bundle (incl. Tracing) 51.86 KB CDN Bundle (incl. Logs, Metrics) 33.47 KB CDN Bundle (incl. Tracing, Logs, Metrics) 53.76 KB CDN Bundle (incl. Replay, Logs, Metrics) 73.92 KB CDN Bundle (incl. Tracing, Replay) 89.09 KB CDN Bundle (incl. Tracing, Replay, Logs, Metrics) 90.99 KB CDN Bundle (incl. Tracing, Replay, Feedback) 95.08 KB CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) 97.02 KB CDN Bundle - uncompressed 92.1 KB CDN Bundle (incl. Tracing) - uncompressed 153.62 KB CDN Bundle (incl. Logs, Metrics) - uncompressed 98.5 KB CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed 159.45 KB CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed 226.91 KB CDN Bundle (incl. Tracing, Replay) - uncompressed 272.39 KB CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed 278.21 KB CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 285.77 KB CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed 291.58 KB @sentry/nextjs (client) 56.39 KB @sentry/sveltekit (client) 51.82 KB @sentry/core/server 43.26 KB @sentry/core/browser 13.62 KB @sentry/node 151.41 KB @sentry/node/import (ESM hook with diagnostics-channel injection) 79.75 KB @sentry/node - without tracing 93.52 KB @sentry/node - without channel injection 132.48 KB @sentry/aws-serverless 101.5 KB @sentry/cloudflare (withSentry) - minified 193.25 KB @sentry/cloudflare (withSentry) 480.29 KB @sentry/nextjs/cloudflare (withSentry) - minified 213.35 KB 11.9.0
22 Oct 2026Rename
diagnostic_channel, fetch and gRPC span originsSome span origins changed their names to match the other v11 origins:
If you have
ignoreSpansrules, queries or alerts on the old origins, change them to use the new origins.deno: Add incoming request options to
denoServeIntegrationdenoServeIntegrationnow acceptsignoreRequestBody,ignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreatedandonSpanEnd, with the same meaning as indenoHttpIntegration. The callbacks receive the webRequest.ignoreStaticAssetsdefaults totrue, soDeno.serveno longer creates spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, setdenoServeIntegration({ ignoreStaticAssets: false }).Deno.servespans 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.servedenoServeIntegrationnow records a request session for each incoming request, asdenoHttpIntegrationdoes fornode:http. This gives release health and crash-free rates forDeno.serveapps. Sessions are sent only when areleaseis set. To turn them off, setdenoServeIntegration({ sessions: false }).sessionFlushingDelayMSsets how long the SDK waits before it sends the session aggregate.
Important Changes
Rename
diagnostic_channel, fetch and gRPC span originsSome span origins changed their names to match the other v11 origins:
auto.graphql.diagnostic_channelis nowauto.graphql.graphql.auto.db.redis.diagnostic_channel,auto.db.mysql2.diagnostic_channelandauto.db.mongoose.diagnostic_channelnow end in.native_channel.auto.http.wintercg_fetchis nowauto.http.fetch, as on Bun, Deno and Cloudflare.auto.grpc.serverlessis nowauto.grpc.google_cloud.
If you have
ignoreSpansrules, queries or alerts on the old origins, change them to use the new origins.deno: Add incoming request options to
denoServeIntegrationdenoServeIntegrationnow acceptsignoreRequestBody,ignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreatedandonSpanEnd, with the same meaning as indenoHttpIntegration. The callbacks receive the webRequest.ignoreStaticAssetsdefaults totrue, soDeno.serveno longer creates spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, setdenoServeIntegration({ ignoreStaticAssets: false }).Deno.servespans 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.servedenoServeIntegrationnow records a request session for each incoming request, asdenoHttpIntegrationdoes fornode:http. This gives release health and crash-free rates forDeno.serveapps. Sessions are sent only when areleaseis set. To turn them off, setdenoServeIntegration({ sessions: false }).sessionFlushingDelayMSsets how long the SDK waits before it sends the session aggregate.deno: Register channel injection hooks from
init()Sentry.init()in@sentry/denonow registers the diagnostics-channel injection hooks, as@sentry/nodedoes. The channel integrations now record spans without--preload=npm:@sentry/deno/import, for modules that you import afterinit(). To also instrument modules that load beforeinit(), such as static imports in your entry module, keep the preload. Withdebug: true, the SDK logs a warning when no injection is active.On Node.js, tracing-hooks messages now show with
debug: trueinstead of withDEBUG=@apm-js-collab/*.nextjs: Add a tunnel route handler that sends only the event payload to Sentry
The
tunnelRouteoption 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 yourtunnelRouteoption:// 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
cacheComponentsenabled 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, registerNextSentryPropagatorinstead and pass your tracer provider tomarkPrerendersOnTracerProvider, so that your prerendered pages carry no trace information either.nextjs: Send tunnel route requests with
credentials: 'omit'With
tunnelRouteand no tunnel route handler,@sentry/nextjsnow sends events from the browser withcredentials: '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 browserSentry.initcall:// instrumentation-client.ts Sentry.init({ transportOptions: { fetchOptions: { credentials: 'same-origin' } }, });nitro: Report a single
http.serverspan per requestA Nitro request now creates only one
http.serverspan. The nestedhttp.serverspans with the originsauto.http.nitro.srvxandauto.http.nitro.h3are removed. h3 route handlers now get ahandlerspan, and middleware spans are direct children of thehttp.serverspan. If you have queries or alerts on the removed spans, change them to use thehttp.serverspan or thehandlerspan.Use
auto.http.http_serverorigin for allnode:httpserver spansOn Bun and Deno,
node:httpserver spans now have the originauto.http.http_serverinstead ofauto.http.server, as on Node.js. On Node.js, nothing changes.Bun.servespans keepauto.http.bun.serveandDeno.servespans keepauto.http.deno. If you haveignoreSpansorbeforeSendSpanrules, queries or alerts onauto.http.server, change them to useauto.http.http_server.
Other Changes
browser: Add
LoaderSentrytype exportcloudflare: Add
isStreamingResponseoption and detect streamed RSC responsescore: Add
dataCollection.mcpoptioncore: Limit the body size of tunnel requests
nextjs: Link
use cachehits to their fill across instancesnextjs: Wait for the resumed part of a document before starting the pageload
nitro: Merge the nitro integrations into a single
nitroIntegrationserver-utils: Emit
execute_toolspans for Anthropic'sbeta.messages.toolRunner()astro: Defer to
@sentry/cloudflare/viteon Cloudflare Workersaws-serverless: End the
function.awsspan when a callback-style handler calls backbrowser: Skip profiling for unsampled active root spans
bundler-plugins: Check
globalThisbeforeglobalin the injected snippetbundler-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_metricdata category for metrics rate limits and client reportsdeno: 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:httpserver instrumentationnode: 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.causeis not an Errorreact: 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!
bun: Add incoming request options and request sessions to
bunServerIntegrationbunServerIntegrationnow accepts the same options asdenoServeIntegration:ignoreRequestBody,ignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreated,onSpanEnd,sessionsandsessionFlushingDelayMS. The callbacks receive the webRequest.Bun.servenow records a request session for each incoming request. Sessions are sent only when areleaseis set. To turn them off, setbunServerIntegration({ sessions: false }).ignoreStaticAssetsdefaults totrue, soBun.serveno longer creates spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, setbunServerIntegration({ ignoreStaticAssets: false }).Bun.servespans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled. Errors thrown forOPTIONSandHEADrequests are now captured.node: Add
onSpanEndtohttpIntegrationhttpIntegrationandhttpServerSpansIntegrationnow acceptonSpanEnd, 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.bun: Inject debug IDs and upload source maps in
sentryBunPluginsentryBunPluginfrom@sentry/bun/pluginnow accepts the same options assentryEsbuildPlugin(org,project,authToken,release,sourcemaps, ...). WhenBun.buildwrites source maps tooutdir, 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 runsentry sourcemap injectandsentry sourcemap uploadafter the build.Like the other bundler plugins,
sentryBunPluginnow sends build telemetry and injects the release it detects (for example, from git). To turn off telemetry, settelemetry: false.
Dependency tracking · free for 3 projects
Know when your own dependencies move
@sentry/core shipped a new major in the last 12 months, among 78 releases. inlinr shows which of your projects are behind, and what the upgrade breaks.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Registry facts last checked 9 Nov 2026. Releases and advisories last read 9 Nov 2026.