You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(v10/effect): Capture errors through the Effect v4 ErrorReporter API (#24445)
On Effect v4, Sentry.effectLayer now registers a Sentry ErrorReporter. Failures that pass through Effect.withErrorReporting, ErrorReporter.report or the built-in HTTP and RPC reporting boundaries are captured automatically, with ErrorReporter.ignore, ErrorReporter.severity and ErrorReporter.attributes annotations respected. Nothing changes on Effect v3.
Other Changes
feat(v10/core): Accept a CollectBehavior shorthand for dataCollection.httpHeaders (#24339)
fix(v10/browser): Release the XHR virtualError once the request completed (#24307)
fix(v10/browser-utils): Skip nullish LCP entries in vendored web-vitals (#24349)
fix(v10/bundler-plugins): Stamp debug IDs onto emitted source maps when disable-upload is set (#24332)
fix(v10/core): Don't instrument the SDK's own envelope requests (#24276)
fix(v10/nextjs): Only include emitted chunk directories in Turbopack sourcemap upload (#24295)
fix(v10/nitro): Import from nitro/h3 instead of h3 directly (#24444)
fix(v10/node-core): Don't recurse in logAndExitProcess on a broken stdio pipe (#24353)
fix(v10/nuxt): Detect Nitro version via the app's Nuxt dependency chain (#24025)
fix(v10/replay): Don't rewrite already-emitted nodes when syncing mirror attributes (#23588)
feat(v10/nextjs): Add @sentry/nextjs/config entry point (#23766)
withSentryConfig is now available from @sentry/nextjs/config, the path it moves to in v11. Importing it from @sentry/nextjs still works on v10 but logs a warning once, so you can change your next.config file today and upgrade to v11 without touching it again.
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.
The new rpcTracePropagationBindings option names the env bindings 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 over enableRpcTracePropagation, 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
fix(v10/astro): support astro v7 route patterns properly (#23657)
fix(v10/bundler-plugins): Preserve full file path in component annotation source maps (#23595)
fix(v10/core): Store child span timeout handle in _childSpanTimeoutID (#23673)
fix(v10/node): Only end the process session when it is still ok (#23731)
fix(v10/react-router): Use react-router's own instrumentation types instead of a mirrored copy (#23589)
fix(v10/replay): Suppress Worker destroyed error on session expiry (#23654)
fix(v10/server-utils): Keep orchestrion registration out of tree-shaking (#23591)
fix(v10/server-utils): Stop shipping orchestrion bundler plugins as production dependencies (#23667)
fix(v10/server-utils): Support openai v7 in auto-instrumentation (#23713)
fix(v10/sveltekit): Detect native tracing in flattened SvelteKit 3 config (#23656)
Internal Changes
chore(v10): Add external contributor to CHANGELOG.md (#23626)
docs(v10): Changelog + contributor credit for AI caller-handled error fixes (#23641)
test(v10/e2e): Fix scripts for nuxt dev server (#23658)
test(v10/e2e): Look up events via the organization trace endpoint (#23680)
test(v10/e2e): Look up the symbolicated event via the eventids endpoint (#23681)
The enableLogs client option now defaults to true, so Sentry Logs work without any manual opt-in. Nothing is captured unless you call the Sentry.logger.* APIs or add a log-forwarding integration (such as consoleLoggingIntegration, pinoIntegration, or the winston transport), and you can set enableLogs: false to 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.
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer TIP This summary will be updated as you push new changes.
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.47.0
chore(deps): update dependency @sentry/node to v10.48.0
Apr 9, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.48.0
chore(deps): update dependency @sentry/node to v10.49.0
Apr 16, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.49.0
chore(deps): update dependency @sentry/node to v10.50.0
Apr 23, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.50.0
chore(deps): update dependency @sentry/node to v10.51.0
Apr 29, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.51.0
chore(deps): update dependency @sentry/node to v10.52.0
May 7, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.52.0
chore(deps): update dependency @sentry/node to v10.53.0
May 12, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.53.0
chore(deps): update dependency @sentry/node to v10.53.1
May 12, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.53.1
chore(deps): update dependency @sentry/node to v10.54.0
May 26, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.54.0
chore(deps): update dependency @sentry/node to v10.55.0
May 28, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.55.0
chore(deps): update dependency @sentry/node to v10.56.0
Jun 2, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.56.0
chore(deps): update sentry-javascript monorepo to v10.56.0
Jun 2, 2026
renovateBot
changed the title
chore(deps): update sentry-javascript monorepo to v10.56.0
chore(deps): update sentry-javascript monorepo to v10.57.0
Jun 9, 2026
renovateBot
changed the title
chore(deps): update sentry-javascript monorepo to v10.57.0
chore(deps): update sentry-javascript monorepo to v10.58.0
Jun 15, 2026
renovateBot
changed the title
chore(deps): update sentry-javascript monorepo to v10.58.0
chore(deps): update sentry-javascript monorepo to v10.59.0
Jun 19, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.65.0
chore(deps): update dependency @sentry/node to v10.66.0
Jul 16, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.66.0
chore(deps): update dependency @sentry/node to v10.67.0
Jul 20, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.67.0
chore(deps): update dependency @sentry/node to v10.68.0
Jul 24, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.68.0
chore(deps): update dependency @sentry/node to v10.69.0
Jul 29, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.69.0
chore(deps): update dependency @sentry/node to v10.70.0
Aug 10, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.70.0
chore(deps): update dependency @sentry/node to v10.71.0
Aug 24, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.71.0
chore(deps): update dependency @sentry/node to v10.72.0
Aug 28, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.72.0
chore(deps): update dependency @sentry/node to v10.73.0
Aug 31, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.73.0
chore(deps): update dependency @sentry/node to v10.74.0
Sep 9, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.74.0
chore(deps): update dependency @sentry/node to v10.75.0
Sep 16, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.75.0
chore(deps): update dependency @sentry/node to v10.75.1
Sep 21, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.75.1
chore(deps): update dependency @sentry/node to v10.75.2
Sep 22, 2026
renovateBot
changed the title
chore(deps): update dependency @sentry/node to v10.75.2
chore(deps): update dependency @sentry/node to v10.75.3
Sep 23, 2026
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
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.45.0→10.75.3Release Notes
getsentry/sentry-javascript (@sentry/node)
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 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](https://redirectConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ 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.