chore(deps): update dependency @sentry/node to v10 - #44
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/major-sentry-javascript-monorepo
branch
3 times, most recently
from
May 28, 2024 02:17
9438e66 to
7bf8ccc
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
May 31, 2024 14:54
7bf8ccc to
328baf5
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
June 12, 2024 11:48
dfe9754 to
544f767
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
June 26, 2024 20:27
5a5e80a to
7b5653c
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
July 5, 2024 02:28
51f39da to
a1236e3
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
July 11, 2024 05:48
a87fb41 to
14eb33e
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
July 26, 2024 02:41
5857b0b to
88153b9
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
August 6, 2024 23:48
e06ce69 to
49ad210
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
August 15, 2024 05:52
cd14a08 to
dfbca53
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
August 28, 2024 02:23
dfbca53 to
a45af83
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
September 10, 2024 20:50
535907f to
2604ff4
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
September 25, 2024 18:00
327e1e5 to
134d6b5
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 3, 2024 02:21
134d6b5 to
b393a29
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
December 14, 2024 02:04
eb9685b to
7369130
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
December 21, 2024 02:52
7369130 to
0fa9015
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
January 9, 2025 12:10
0fa9015 to
9640076
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
January 23, 2025 04:22
382f014 to
84c42dc
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
February 4, 2025 03:59
0a1c03d to
344031b
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
February 12, 2025 04:08
344031b to
9021c4f
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
February 15, 2025 00:07
9021c4f to
e1629f7
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
March 1, 2025 19:31
4e4ce54 to
446b519
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
March 7, 2025 23:54
446b519 to
1040b71
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
March 21, 2025 20:08
79382fe to
e04ae1d
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
March 29, 2025 11:35
4e4d44e to
1ef6948
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
April 8, 2025 20:22
010d887 to
43cf147
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
April 19, 2025 07:44
43cf147 to
4645baa
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
May 2, 2025 03:58
9c0fb76 to
b29a871
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
May 16, 2025 00:04
34ad36c to
1d13d41
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
May 24, 2025 12:07
1d13d41 to
33d5a0e
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
June 6, 2025 16:31
4a42001 to
fbce1f0
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
June 14, 2025 12:07
fbce1f0 to
1d7ab03
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:
^7.42.0→^10.75.0Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
getsentry/sentry-javascript (@sentry/node)
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)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 📦
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.