Repository navigation
fix(deps): update dependency @sentry/browser to v11 - #1747
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
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 26, 2026 22:04
8d243d7 to
0f8d465
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 27, 2026 00:32
0f8d465 to
d1d91de
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 27, 2026 05:56
d1d91de to
61e4de8
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 27, 2026 15:06
61e4de8 to
48ae196
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 28, 2026 02:10
48ae196 to
da49538
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 29, 2026 10:39
da49538 to
9403441
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
September 29, 2026 17:30
9403441 to
199ef4a
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 1, 2026 17:41
199ef4a to
b78aa44
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 1, 2026 22:26
b78aa44 to
2a4ab92
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 3, 2026 21:55
3f63cf9 to
5c50711
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 4, 2026 00:34
5c50711 to
9113150
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 4, 2026 04:50
9113150 to
8c12d0c
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 4, 2026 13:41
8c12d0c to
6c9f5c6
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 5, 2026 01:46
6c9f5c6 to
b6d6dae
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 5, 2026 04:25
b6d6dae to
e443aa4
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 5, 2026 15:39
e443aa4 to
953c746
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 5, 2026 21:44
953c746 to
455c130
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 6, 2026 02:06
455c130 to
cd162dc
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 6, 2026 05:56
cd162dc to
f2c40a1
Compare
This branch had an error being 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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
10.76.0→11.7.0Release Notes
getsentry/sentry-javascript (@sentry/browser)
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!
v11.5.0Compare Source
Important Changes
feat(core): Warn on repeated
Sentry.init()and unbind the client onclose()(#24962)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. CallSentry.init()once, or callawait Sentry.close()before you call it again.Sentry.close()now unbinds the client it closes, so afterclose(),getClient()returnsundefined,isInitialized()returnsfalse, and a laterinit()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/nextjsand@sentry/remixnow return the active client from a repeatedinit()call, notundefined.Other Changes
code.file.pathtouse cachefill spans (#24988)initinside a request of@sentry/cloudflare(#24996)experimental_telemetry.metadataon gen_ai spans (#24721)beforeSendSpannull return warning (#24129)Internal Changes
@sentry/conventionsto 0.26.0 (#25073)isObjectLikefor object guards (#25058)serverSpanHooks.ts(#24997)nuxt/server(#25093)Work in this release was contributed by @minwookshin. Thank you for your contribution!
v11.4.0Compare Source
v11.3.0Compare Source
Important Changes
Remix 3 support (alpha, may break in minor releases)
feat(nextjs): Add
cache_originspan links touse cachehit spans (#24821)A
cache.getspan for a"use cache"hit now carries a span link (sentry.link.type: 'cache_origin') to thecache.putspan of the request that filled the cache entry, connecting the trace that reads a cached value to the trace that produced it.fix(cloudflare): Don't treat DO constructor work as incoming RPC calls (#24829)
Durable Object constructors now run in their own isolation scope. When work that the constructor starts, for example a
blockConcurrencyWhilecallback, 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()andsetContext()in a constructor now apply only to that constructor work. They no longer reach laterfetch, RPC oralarminvocations, because the scope they used to write to is shared by every Durable Object and handler in the isolate. UseinitialScopefor static data, and set per-instance data in each handler.fix(effect)!: Change peerDependency to v4 and fix currentSpan (#24940)
@sentry/effectnow requires a stable Effect v4 release. Effect v4 beta and release candidate versions are no longer supported.@sentry/effectis in alpha, so this ships in a minor release.Other Changes
client.sendEnvelope(#24896)Internal Changes
4013fc6to36c7292(#24949)Work in this release was contributed by @Shubham-Padkonde and @tobias-schnabel. Thank you for your contributions!
v11.2.0Compare Source
Important Changes
feat(hono): add orchestrion-based auto-instrumentation (#24497)
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.
feat(node/bun): Enable dedupeIntegration by default (#24794)
@sentry/nodeand@sentry/bunnow includededupeIntegrationin 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').feat(remix): Instrument Remix 3 server requests via fetch-router (#24801)
On Remix 3, the SDK now adds the matched route as
http.route, the response status and a low-cardinality name to thehttp.serverspan of eachfetch-routerrequest. Start the app with--import @sentry/remix/v3/nodein place of--import remix/node-tsx.Other Changes
bunRuntimeMetricsIntegration(#24892)fmt/parameterizemessages (#24770)nextis called (#24854)rolldownOptionsin instrumentation file plugin (#24863)Internal Changes
externallabel on PRs of external contributors (#24825)dedupeIntegration(#24893)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.