Repository navigation
Update dependency @sentry/react to v11 - #844
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
March 31, 2026 12:40
da6ecfd to
157b834
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
April 16, 2026 18:07
337528b to
7c6780d
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
April 29, 2026 15:52
d3e4be2 to
a708462
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
May 12, 2026 17:32
a2d6f5b to
81da966
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
May 28, 2026 19:46
cb9d59a to
7a1f5d8
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
June 2, 2026 17:11
7a1f5d8 to
7dcfc39
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
June 16, 2026 00:33
ba6cbba to
88dd946
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
June 19, 2026 16:29
88dd946 to
21d581c
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
June 25, 2026 10:35
98124e5 to
9315dfc
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
July 1, 2026 22:06
3bbcaf8 to
2702757
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
July 10, 2026 10:58
4ee600d to
97b0e9c
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
July 21, 2026 02:51
c5ac4bb to
f10770d
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
July 29, 2026 13:30
2c74f63 to
84f1c19
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
August 10, 2026 12:47
84f1c19 to
00bac55
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
August 31, 2026 17:48
4557909 to
c7fbbbd
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 9, 2026 19:40
c7fbbbd to
16691c5
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
September 22, 2026 12:03
6292574 to
2e12c07
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 23, 2026 21:50
2e12c07 to
9faea03
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
5 times, most recently
from
October 5, 2026 17:28
85e27e0 to
fcbc2ce
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
October 13, 2026 02:34
1c682d2 to
032baca
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 15, 2026 11:12
032baca to
ee0d9aa
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 23, 2026 12:28
ee0d9aa to
938e4f8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
^7.0.0→^11.0.0Release Notes
getsentry/sentry-javascript (@sentry/react)
v11.9.0Compare Source
Important Changes
feat: Rename
diagnostic_channel, fetch and gRPC span origins (#25601)Some 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.feat(deno): Add incoming request options to
denoServeIntegration(#25493)denoServeIntegrationnow 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.feat(deno): Record request sessions for
Deno.serve(#25496)denoServeIntegrationnow 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.feat(deno): Register channel injection hooks from
init()(#25546)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/*.feat(nextjs): Add a tunnel route handler that sends only the event payload to Sentry (#25456)
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: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.
feat(nextjs): Never emit trace meta tags from a prerender (#25141)
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.feat(nextjs): Send tunnel route requests with
credentials: 'omit'(#25509)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 browser
Sentry.initcall:feat(nitro): Report a single
http.serverspan per request (#25295)A 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.fix: Use
auto.http.http_serverorigin for allnode:httpserver spans (#25604)On 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
LoaderSentrytype export (#25357)isStreamingResponseoption and detect streamed RSC responses (#24932)dataCollection.mcpoption (#25553)use cachehits to their fill across instances (#25448)nitroIntegration(#25349)execute_toolspans for Anthropic'sbeta.messages.toolRunner()(#25320)@sentry/cloudflare/viteon Cloudflare Workers (#25347)function.awsspan when a callback-style handler calls back (#25543)globalThisbeforeglobalin the injected snippet (#25365)trace_metricdata category for metrics rate limits and client reports (#25606)@opentelemetry/api1.9 again (#25684)node:httpserver instrumentation (#25592)error.causeis not an Error (#25542)Internal Changes
@types/nodeto 20 (#25501).binscripts (#25635)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!
feat(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.feat(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.feat(bun): Inject debug IDs and upload source maps in
sentryBunPlugin(#25670)sentryBunPluginfrom@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.v11.8.0Compare Source
Important Changes
feat(bundler-plugins): Release
@sentry/webpack-plugin,@sentry/vite-plugin,@sentry/rollup-pluginand@sentry/esbuild-pluginfrom the SDK repository (#25095)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-pluginsentry point, which we recommend for new projects. The plugin options do not change, but the update brings these breaking changes:@sentry/webpack-pluginrequires webpack 5.1 or higher. The@sentry/webpack-plugin/webpack5entry point still works and exports the same plugin as@sentry/webpack-plugin.sentryCLI SDK instead of@sentry/cli. Sentry self-hosted 26.4.2 or higher is supported. Lower versions may continue to work.VERCEL_TARGET_ENV(production,previewor a custom name) as their environment, instead ofvercel-productionorvercel-preview. To keep the old value, setrelease.deploy.env.feat(server-utils): Instrument the OpenAI decisions API as
gen_ai.decidespans (#25285)OpenAI
decisions.createcalls now creategen_ai.decidespans.Other Changes
urlQueryParamsto the Referer header (#25324)mainis a package (#25343)output(#25312)sveltekit.endpointspan (#25376)Internal Changes
Work in this release was contributed by @kunal649 and @mketiku. Thank you for your contributions!
v11.7.0Compare Source
Important Changes
feat(cloudflare): Add opt-in cron monitoring for Cron Triggers (#25014)
The new
cronTriggersIntegrationsends check-ins for Cron Triggers. Each check-in includes the schedule fromcontroller.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:The
monitorSlugfunction can also return monitor settings, for example{ monitorSlug: 'daily-report', maxRuntime: 30 }, orundefinedto send no check-ins for a trigger. WithoutmonitorSlug, the SDK derives the slug from the cron expression. If you deploy withwranglerdirectly, pass the same integration toSentry.withSentry.feat(node): Add neonIntegration for @neondatabase/serverless (#25164, #25176)
The new
neonIntegrationcreatesdbspans for queries of the@neondatabase/serverlessdriver: for the WebSocketClientandPool, and for the HTTPneon()function. This includes theneon-httpandneon-serverlessadapters of Drizzle. The integration is on by default when tracing is enabled.feat(node): Stop sending the process session once request sessions are tracked (#24915)
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 withhttpServerIntegration({ 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.feat(server-utils): Record decide calls as
gen_ai.decidespans (#25270, #25272, #25274, #25281)Vercel AI
experimental_decidecalls, Mastra classifier evaluations, TypeSafe and LangChain Jev calls, and Workers AI calls to TypeSafe Jev and Cloudflare Clef models now createdecide <model>spans with the opgen_ai.decide. Before, these spans had the opgen_ai.evaluate, which is now deprecated in the Sentry conventions. If you usegen_ai.evaluatein queries, alerts or dashboards, change it togen_ai.decide.fix(browser): Apply
urlQueryParamsto more URLs (#25262, #25289)The
dataCollection.urlQueryParamsoption now also filters the query parameters of these URLs:event.request.urlbrowser.*andresource.*span names withtraceLifecycle: 'static'lcp.urlandbrowser.web_vital.lcp.urlui.element.urlattribute ofelementTimingIntegrationBefore this fix, these URLs could send sensitive query values, for example
?jwt=..., to Sentry.fix(nextjs): Apply top-level
bundleSizeOptimizationsto webpack and Turbopack builds (#24818)The top-level
bundleSizeOptimizationsoption now removes unused SDK code in webpack and in Turbopack builds. Before, the tree-shaking options had no effect on Turbopack. Thewebpack.treeshakeoption is deprecated. It still works, but when you set both options,bundleSizeOptimizationstakes precedence.Other Changes
@nuxt/kit4.6 (#25138)spanclient report outcomes when discarding transactions (#25006)@sentry/server-runtime-injectionexternal on Nitro v3 (#24901)Internal Changes
@sentry/conventionsto 0.27.0 (#25264)conditionalTestwith asupportshelper (#25202)NODE_VERSIONandRUNTIMEfrom the test utils (#25292)nuxt/serverin the nuxt-5 E2E app (#25232)Work in this release was contributed by @Philip-Nwabuwa and @4ktLuffy. Thank you for your contributions!
v11.6.0Compare Source
Important Changes
feat(nextjs): Add
@sentry/nextjs/cloudflare(#24998)The new
@sentry/nextjs/cloudflareentry point exportswithSentryfor the Worker entry of a Next.js app on Cloudflare Workers, for example.open-next/worker.jsof OpenNext. It iswithSentryof@sentry/cloudflarewith the Next.js server handling added, so a Next.js app on Workers gets the same spans as on Node.js.feat(server-utils): Add instrumentation for pi-durable (#24993)
The new
piDurableIntegrationtraces agents built with pi-durable: each run, with its model requests and tool calls.fix(core): Correct sleep clock drift on telemetry timestamps (#23054)
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 theperformance.now()duration since the span start, like in OpenTelemetry (#24903).Other Changes
Internal Changes
@sentry/nextjs/cloudflare(#25000)no-unsafe-random-apisrule (#25123)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.