fix(deps): update sentry sdk (major) - #679
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
3 times, most recently
from
May 23, 2024 17:17
731bebf to
e5dfdc6
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
2 times, most recently
from
May 29, 2024 16:58
2f952ad to
c5fba93
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
3 times, most recently
from
June 12, 2024 11:05
f087a6d to
b8b94df
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
3 times, most recently
from
June 25, 2024 12:07
d788adf to
aad30cb
Compare
jmkoenig
added a commit
to cbsi-cmg/sentry-module
that referenced
this pull request
Jun 26, 2024
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
2 times, most recently
from
July 4, 2024 11:31
8cc1854 to
15f81d8
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
3 times, most recently
from
July 10, 2024 13:23
a70d9d5 to
ccc6956
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
2 times, most recently
from
July 19, 2024 12:14
a62d957 to
222a240
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
2 times, most recently
from
July 31, 2024 11:01
f1d9152 to
7b9c8d5
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
3 times, most recently
from
August 6, 2024 14:34
9498476 to
2de5fd8
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
2 times, most recently
from
August 14, 2024 07:47
8c98c5c to
3ed9fca
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
4 times, most recently
from
August 27, 2024 09:04
5f5b27c to
54dfeb0
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
3 times, most recently
from
October 10, 2024 17:09
136baea to
4a7bf12
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
from
October 21, 2024 12:44
4a7bf12 to
7413ed4
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
2 times, most recently
from
November 5, 2024 17:08
bbd364f to
ecc916f
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
2 times, most recently
from
November 19, 2024 15:47
ebb7231 to
7017f0d
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
2 times, most recently
from
November 22, 2024 14:27
8536370 to
d93b57e
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
2 times, most recently
from
December 2, 2024 16:57
3151e04 to
1e2def1
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
5 times, most recently
from
December 17, 2024 13:51
5ef98a2 to
53f5ec3
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
2 times, most recently
from
December 18, 2024 21:06
3957b91 to
e145789
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
from
January 7, 2025 13:43
e145789 to
75f4d20
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
from
January 15, 2025 12:08
75f4d20 to
991eb42
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
from
January 15, 2025 18:44
991eb42 to
b8ca25e
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
3 times, most recently
from
January 28, 2025 19:26
08794c7 to
9d4fc1b
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-sdk
branch
3 times, most recently
from
January 31, 2025 11:43
e179a52 to
2ae817b
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.119.0→^10.74.0^7.119.0→^10.74.07.119.0→10.74.0^7.119.0→^8.55.2^7.119.0→^10.74.02.22.3→5.4.0Release Notes
getsentry/sentry-javascript (@sentry/core)
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 📦
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.