fix(deps): update sentry-javascript monorepo to v10.75.3 - #215
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 25, 2026 11:44
63c898d to
e84ed6a
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 25, 2026 13:01
e84ed6a to
bbd1cda
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 25, 2026 17:35
bbd1cda to
1ec0578
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 25, 2026 21:02
1ec0578 to
4609e40
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 26, 2026 04:27
4609e40 to
4fee6f4
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 29, 2026 13:49
4fee6f4 to
b2300eb
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
August 10, 2026 14:15
b2300eb to
9338078
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
August 25, 2026 14:17
9338078 to
f09aee4
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
August 28, 2026 15:46
f09aee4 to
a103f6c
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
August 28, 2026 20:09
a103f6c to
02a82eb
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
August 31, 2026 18:06
02a82eb to
7f4e7c2
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
September 9, 2026 23:09
7f4e7c2 to
6fb42b2
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
September 16, 2026 20:09
6fb42b2 to
04463b9
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
September 21, 2026 23:58
04463b9 to
0d8ec62
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
September 22, 2026 14:06
0d8ec62 to
ee796f1
Compare
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
September 24, 2026 02:02
ee796f1 to
94e2d82
Compare
This branch was successfully 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.53.1→10.75.310.53.1→10.75.3Release Notes
getsentry/sentry-javascript (@sentry/opentelemetry)
v10.75.3Compare Source
Internal Changes
Bundle size 📦
v10.75.2Compare Source
dataCollection.urlQueryParamsto collected URLs and query strings (#24572)v10.75.1Compare Source
Bundle size 📦
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)Bundle size 📦
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!
Bundle size 📦
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
Bundle size 📦
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 wiConfiguration
📅 Schedule: (in timezone Asia/Bangkok)
🚦 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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.