chore(deps): update dependency @sentry/browser to v10.72.0 - #1235
Draft
renovate[bot] wants to merge 1 commit into
Draft
chore(deps): update dependency @sentry/browser to v10.72.0#1235renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## staging #1235 +/- ##
========================================
Coverage 77.59% 77.59%
========================================
Files 54 54
Lines 1406 1406
========================================
Hits 1091 1091
Misses 315 315 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
February 24, 2026 18:42
bf42d85 to
fa0c8ee
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
2 times, most recently
from
March 3, 2026 18:16
323e850 to
c918e95
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
March 10, 2026 12:50
c918e95 to
8332412
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
March 17, 2026 18:11
8332412 to
21345bd
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
March 19, 2026 17:02
21345bd to
4a0f8ab
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
2 times, most recently
from
March 31, 2026 13:01
ed88489 to
b7082f5
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
April 9, 2026 17:22
b7082f5 to
e76f7c8
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
April 16, 2026 15:20
e76f7c8 to
9f28ba5
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
April 23, 2026 15:11
9f28ba5 to
9e21944
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
April 29, 2026 15:43
9e21944 to
424273e
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
May 7, 2026 12:42
424273e to
7ea11ea
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
May 12, 2026 15:33
7ea11ea to
f8de727
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
June 19, 2026 17:55
ada23be to
4f183b4
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
2 times, most recently
from
June 25, 2026 11:38
7a00480 to
e0a07b0
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
June 26, 2026 14:57
e0a07b0 to
763d4f8
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 1, 2026 23:39
763d4f8 to
6a87b0c
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 7, 2026 15:37
6a87b0c to
a057078
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 10, 2026 17:42
a057078 to
c854622
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 16, 2026 16:50
c854622 to
8bd65c7
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 21, 2026 03:06
8bd65c7 to
7634f37
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 24, 2026 19:37
7634f37 to
7e90bbc
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 29, 2026 13:08
7e90bbc to
d807e86
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
August 10, 2026 15:56
d807e86 to
488b437
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
August 25, 2026 18:00
488b437 to
4497b9c
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
August 28, 2026 17:09
4497b9c to
8f792be
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.
This PR contains the following updates:
10.38.0→10.72.0Release Notes
getsentry/sentry-javascript (@sentry/browser)
v10.72.0Compare Source
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.feat(v10/cloudflare): Add
rpcTracePropagationBindings(#23737, #23738)The new
rpcTracePropagationBindingsoption names theenvbindings 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 overenableRpcTracePropagation, 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
_childSpanTimeoutID(#23673)Internal Changes
Work in this release was contributed by @ryanrho-mercor, @lux-in-tenebris-lucet, and @suhailopensource. Thank you for your contributions!
Bundle size 📦
v10.71.0Compare Source
Important Changes
The
enableLogsclient option now defaults totrue, so Sentry Logs work without any manual opt-in. Nothing is captured unless you call theSentry.logger.*APIs or add a log-forwarding integration (such asconsoleLoggingIntegration,pinoIntegration, or the winston transport), and you can setenableLogs: falseto 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
scope.clear()method (#23231)Headersinstances (#23241)captureExceptionfrom scope, not fromClient(#23280)Internal Changes
Bundle size 📦
v10.70.0Compare Source
@sentry/node-cpu-profilerto 2.4.3 (#22992)@solidjs/routerv1 (#23163)onRequestpath (#22985)beforeSendwhile preserving session updates (#22819)meriyahissue forstandalonebuild (#23055)sourcemaps.disablewhenunstable_sentryVitePluginOptionsis set (#22966)<Routes>unmount (#22948)metricsfrom worker entry point (#23027)Internal Changes
@sentry/coredep to nextjs-16-userfeedback (#23009)sveltekit-3test (#23016)Work in this release was contributed by @davidmurdoch, @Jxxunnn, and @kamilogorek. Thank you for your contributions!
Bundle size 📦
v10.69.0Compare Source
Important Changes
instrumentAgentWithSentryfor Cloudflare Agents (#22786)The Cloudflare SDK adds a new
instrumentAgentWithSentryAPI for Cloudflare Agents. It works likeinstrumentDurableObjectWithSentryforAgentclasses from theagentsSDK and additionally creates spans for@callableRPC methods and automatically sets theconversationIdbased on the agent's name. When building with the Sentry Vite plugin, Agents are instrumented automatically (#22788).Other Changes
CREATE INDEXspans oncf_-prefixed tables (#22767)cf_spans stay filtered (#22766)sentry.originon logs fromSentryEffectLogger(#22806)@apm-js-collab/code-transformer-bundler-plugins(#22678)Internal Changes
Bundle size 📦
v10.68.0Compare Source
cache.keyon dataloader spans and capture redis delete operations ascache.remove(#22389)FirebaseInstrumentationto orchestrion (#22141)http.routeattribute tohttp.serverspans with parameterized routes (#22564)url.fullandurl.pathtohttp.serverspans (#22533)instrumentStateGraphAPI (#22491)url.fullattribute to core fetch instrumentation (#22436)stackFrameVariablesby variable name (#22526)@apm-js-collab/code-transformer-bundler-pluginsto 0.7.1 (#22497)functionToStringIntegrationcausing infinite recursions (#22527)baggage: "undefined"when DSC is missing (#22440)Internal Changes
v10to build and license-compliance branch filters (#22499)defineEnvVarsfrom@sveltejs/kit/env(#22390)Work in this release was contributed by @psh4607 and @trinitiwowka. Thank you for your contributions!
Bundle size 📦
v10.67.0Compare Source
Important Changes
feat(sveltekit): Add support for SvelteKit 3 (#22264)
The SvelteKit SDK now supports the pre-release of SvelteKit 3, including client-side pageload and navigation tracing and server-side native tracing, alongside continued SvelteKit 2 support. No Sentry-specific setup changes are required. The SDK detects your SvelteKit version and picks the right implementation automatically.
Other Changes
Configuration
📅 Schedule: (in timezone Europe/Amsterdam)
🚦 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.