Update all dependencies (major) - #258
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
renovate
Bot
force-pushed
the
renovate/major-all
branch
7 times, most recently
from
January 13, 2025 18:25
ac8a7c5 to
f0303a2
Compare
renovate
Bot
force-pushed
the
renovate/major-all
branch
4 times, most recently
from
January 21, 2025 02:21
3ba90b7 to
42e2e0a
Compare
renovate
Bot
force-pushed
the
renovate/major-all
branch
5 times, most recently
from
January 28, 2025 19:20
31f8f56 to
7bea63c
Compare
renovate
Bot
force-pushed
the
renovate/major-all
branch
5 times, most recently
from
February 5, 2025 11:15
4a3088b to
2fc1e97
Compare
renovate
Bot
force-pushed
the
renovate/major-all
branch
8 times, most recently
from
February 14, 2025 13:47
27bf586 to
402ed8a
Compare
renovate
Bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
March 10, 2025 17:36
cdcc7d2 to
499ef63
Compare
renovate
Bot
force-pushed
the
renovate/major-all
branch
8 times, most recently
from
March 24, 2025 18:38
99b6843 to
1e5c0ee
Compare
renovate
Bot
force-pushed
the
renovate/major-all
branch
6 times, most recently
from
April 3, 2025 17:33
10ae33e to
8037546
Compare
renovate
Bot
force-pushed
the
renovate/major-all
branch
4 times, most recently
from
April 9, 2025 17:44
599ada6 to
6402b3d
Compare
renovate
Bot
force-pushed
the
renovate/major-all
branch
6 times, most recently
from
April 18, 2025 21:29
b7fb0c0 to
0856ac5
Compare
renovate
Bot
force-pushed
the
renovate/major-all
branch
3 times, most recently
from
April 23, 2025 09:47
c1ac279 to
3ce3b4a
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:
7.88.0→10.73.0^6.0.0→^7.0.0^29.1.2→^30.0.0^21.0.0→^30.0.06.14.0→8.69.06.14.0→8.69.0v4→v711.1.0→15.0.08.12.0→10.10.0^5.0.4→^8.0.0^29.1.2→^30.0.0^29.1.2→^30.0.023.0.1→30.0.122.7.1→25.10.04.1.3→6.0.25.3.3→7.0.222.04→24.04Release Notes
getsentry/sentry-javascript (@sentry/node)
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 📦
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 📦
Configuration
📅 Schedule: (UTC)
🚦 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.