fix(deps): update sentry-javascript monorepo to ^10.72.0 - #106
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update sentry-javascript monorepo to ^10.72.0#106renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
2 times, most recently
from
October 24, 2025 21:43
58d5d7b to
91025cb
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
October 27, 2025 12:05
91025cb to
052d9a9
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
2 times, most recently
from
November 8, 2025 16:49
34e8b2f to
f2102c8
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
2 times, most recently
from
November 13, 2025 20:45
c55a364 to
5ce8f0e
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
November 14, 2025 21:52
5ce8f0e to
19e594b
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
November 22, 2025 12:55
19e594b to
6eb4e8d
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
November 27, 2025 20:59
6eb4e8d to
688c9d4
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
2 times, most recently
from
December 5, 2025 17:58
0ad90fb to
30a2b2a
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
December 7, 2025 21:33
30a2b2a to
420a52a
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
December 14, 2025 10:32
420a52a to
f089865
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
December 19, 2025 16:56
f089865 to
cb0cd2e
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
December 21, 2025 14:11
cb0cd2e to
497412c
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
December 22, 2025 13:50
497412c to
513a57f
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
January 30, 2026 14:08
72ff061 to
c8d998f
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
February 1, 2026 17:38
c8d998f to
9ab7930
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
2 times, most recently
from
February 19, 2026 09:58
f1dcc6e to
5308751
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
February 27, 2026 16:55
5308751 to
1d4f00b
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
March 5, 2026 13:03
1d4f00b to
189e16f
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
March 6, 2026 14:41
189e16f to
041387b
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
March 13, 2026 18:48
041387b to
0e571b5
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
March 20, 2026 18:13
0e571b5 to
2a86cb2
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
March 22, 2026 13:59
2a86cb2 to
236c21a
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
March 28, 2026 17:00
236c21a to
390e543
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
2 times, most recently
from
April 3, 2026 13:45
bc0e226 to
d7b97cc
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
2 times, most recently
from
April 12, 2026 17:19
7e95c3c to
819c626
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
April 19, 2026 17:12
819c626 to
2034959
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.10.0→^10.72.0^10.10.0→^10.72.0Release Notes
getsentry/sentry-javascript (@sentry/nestjs)
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 Asia/Karachi)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.