Repository navigation
Update dependency @sentry/react to v11.8.0 - #4460
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
Coverage Report for CI Build 39763848845Coverage remained the same at 47.811%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats💛 - Coveralls |
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
7 times, most recently
from
October 15, 2026 17:10
afdd771 to
5ba944e
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
10 times, most recently
from
October 18, 2026 10:52
aee33d5 to
faf0197
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
9 times, most recently
from
October 18, 2026 14:08
7fe72f8 to
4328ace
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
7 times, most recently
from
October 22, 2026 04:57
cab726e to
5a2cc22
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
October 22, 2026 10:32
5a2cc22 to
1596330
Compare
This branch has not been deployed
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.
This PR contains the following updates:
11.5.0→11.8.0Release Notes
getsentry/sentry-javascript (@sentry/react)
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)Work in this release was contributed by @zkasuran. Thank you for your contribution!
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.