Repository navigation
chore(deps): update sentry packages (minor) - #854
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/sentry-packages
branch
6 times, most recently
from
November 10, 2025 23:00
085072f to
2db60f7
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
2 times, most recently
from
November 12, 2025 01:57
f06921b to
61e2236
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
4 times, most recently
from
November 24, 2025 22:09
c4cafec to
5c5dde1
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
4 times, most recently
from
December 8, 2025 09:15
e3d4431 to
92778a4
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
4 times, most recently
from
December 18, 2025 10:43
2e24b00 to
af6fb8f
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
2 times, most recently
from
December 19, 2025 11:32
cadef44 to
b59cdd4
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
4 times, most recently
from
January 5, 2026 10:38
1e81e6b to
eadff25
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
3 times, most recently
from
January 12, 2026 15:04
ef4b6d8 to
ea409e8
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
2 times, most recently
from
March 5, 2026 16:36
cdc761a to
5d41d48
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
3 times, most recently
from
March 19, 2026 14:52
9b6fa4d to
26a8230
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
from
March 25, 2026 19:12
26a8230 to
735be9b
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
2 times, most recently
from
April 8, 2026 15:57
23ce701 to
f8c18c3
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
from
April 9, 2026 19:44
f8c18c3 to
fb04a4e
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
2 times, most recently
from
April 23, 2026 17:39
23c42dc to
640aa0a
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
from
April 29, 2026 18:04
640aa0a to
1eceeba
Compare
|
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
3 times, most recently
from
May 18, 2026 14:10
73b7303 to
da286d8
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
3 times, most recently
from
June 2, 2026 00:18
b577d36 to
5de5fcf
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
2 times, most recently
from
June 9, 2026 12:47
273b1eb to
bf55635
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
from
June 11, 2026 10:16
bf55635 to
a1c4850
Compare
|
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
2 times, most recently
from
June 19, 2026 16:47
1576146 to
0f4fddb
Compare
renovate
Bot
force-pushed
the
renovate/sentry-packages
branch
3 times, most recently
from
July 2, 2026 00:51
8256f69 to
14f3b0a
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:
10.20.0→10.76.14.4.0→4.9.1Release Notes
getsentry/sentry-javascript (@sentry/tanstackstart-react)
v10.76.1Compare Source
@opentelemetry/apivia the SDK on SvelteKit 3 (#25105)Internal Changes
Bundle size 📦
v10.76.0Compare Source
Internal Changes
Bundle size 📦
v10.75.3Compare Source
Internal Changes
Bundle size 📦
v10.75.2Compare Source
dataCollection.urlQueryParamsto collected URLs and query strings (#24572)v10.75.1Compare Source
v10.75.0Compare Source
Important Changes
feat(v10/effect): Capture errors through the Effect v4
ErrorReporterAPI (#24445)On Effect v4,
Sentry.effectLayernow registers a SentryErrorReporter. Failures that pass throughEffect.withErrorReporting,ErrorReporter.reportor the built-in HTTP and RPC reporting boundaries are captured automatically, withErrorReporter.ignore,ErrorReporter.severityandErrorReporter.attributesannotations respected. Nothing changes on Effect v3.Other Changes
CollectBehaviorshorthand fordataCollection.httpHeaders(#24339)virtualErroronce the request completed (#24307)disable-uploadis set (#24332)v10.74.0Compare Source
user_agent.originalon all spans for consistent filtering (#24226)loadModuledefault parameter against ESM scope (#24154)DEFAULT_IGNORE_ERRORS(#23877)Internal Changes
Work in this release was contributed by @halillusion and @zkasuran. Thank you for your contributions!
v10.73.0Compare Source
Important Changes
feat(v10/nextjs): Add
@sentry/nextjs/configentry point (#23766)withSentryConfigis now available from@sentry/nextjs/config, the path it moves to in v11. Importing it from@sentry/nextjsstill works on v10 but logs a warning once, so you can change yournext.configfile today and upgrade to v11 without touching it again.Other Changes
shouldHandleErroronsetupExpressErrorHandlerandsetupFasitfyErrorHandler(#23734)Internal Changes
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!
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
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!
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
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!
v10.67.0Compare Source
Important Changes
feat(effect): Capture errors through the Effect v4
ErrorReporterAPIOn Effect v4,
Sentry.effectLayernow registers a SentryErrorReporter. Failures that pass throughEffect.withErrorReporting,ErrorReporter.reportor the built-in HTTP and RPC reporting boundaries are captured automatically, withErrorReporter.ignore,ErrorReporter.severityandErrorReporter.attributesannotations respected. Nothing changes on Effect v3.The server SDK now enables the
contextLinesandlinkedErrorsintegrations by default, so captured errors carry source context and theircausechain. No other Node default integration is enabled.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: (UTC)
* * 1 * *)* 0-4,22-23 * * 1-5)* * * * 0,6)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.