fix(deps): update dependency @sentry/vue to v10.64.0#2834
Merged
Conversation
kulmann
approved these changes
Jul 8, 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.63.0→10.64.0Release Notes
getsentry/sentry-javascript (@sentry/vue)
v10.64.0Compare Source
Important Changes
feat(cloudflare): Add
nodejs_compatentrypoint (#21881)The Cloudflare SDK now ships a dedicated
@sentry/cloudflare/nodejs_compatentrypoint for Workers running with thenodejs_compatflag. This entrypoint unlocks Node SDK features on Cloudflare, including theprismaIntegration(#21882) and AI v7 support for thevercelAiIntegration(#21917).This entrypoint is a drop-in replacement, so you can switch your imports from
@sentry/cloudflaredirectly to@sentry/cloudflare/nodejs_compat. To use it, your Worker must set thenodejs_compatcompatibility flag inwrangler.toml/wrangler.jsonc. This will become the default entrypoint in v11.feat: Use Sentry's minimal OpenTelemetry tracer provider by default (#21666, #21680, #21842)
The Node SDK now registers Sentry's own minimal
SentryTracerProviderby default, which creates native Sentry spans directly instead of routing them through the full OpenTelemetry SDK span pipeline. This reduces overhead for the common case where you don't need the full OpenTelemetry tracing stack.If you rely on OpenTelemetry SDK features that the minimal provider doesn't support, you can opt out and fall back to the full OpenTelemetry
BasicTracerProviderby settingopenTelemetryBasicTracerProvider: truein yourSentry.init()options. Providing customopenTelemetrySpanProcessorsalso forces the full provider automatically.Other Changes
sentry.trace_lifecycleattribute (#21850)Middleware.executeroot spans on Node.js runtime (#22013)onBeforeLoad/onResolved(#21975)Internal Changes
app-idwithclient-idin GH workflows (#21914)@opentelemetry/instrumentation-ioredisto orchestrion (#21849)@opentelemetry/instrumentation-hapito orchestrion (#21866)@sentry/conventionsto@sentry/coreand align versions (#21855)@sentry/conventionsand vendor remaining semantic conventions (#21893)injectDiagnosticsfor orchestrion marker (#21987)additionalDependencies(#21878)Work in this release was contributed by @codr and @zenato. Thank you for your contribution!
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.
🔕 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.