[Snyk] Upgrade @sentry/angular from 10.60.0 to 10.65.0 - #2351
Conversation
Snyk has created this PR to upgrade @sentry/angular from 10.60.0 to 10.65.0. See this package in npm: @sentry/angular See this project in Snyk: https://app.snyk.io/org/des-yhy/project/549d215d-7c2d-4c88-ad2b-4fde0727c31d?utm_source=github&utm_medium=referral&page=upgrade-pr
|
This is a minor version upgrade for Notably, version 10.65.0 standardizes URL attributes on pageload and navigation spans to include No breaking changes or mandatory migration steps are documented for Source: Sentry JavaScript SDK Changelog
|
github-actions
Bot
added
the
dependencies
There was a problem hiding this comment.
Pull request overview
Updates the app’s Sentry Angular SDK dependency as part of dependency maintenance (Snyk-driven), aiming to keep monitoring/error-reporting libraries current.
Changes:
- Bumps
@sentry/angularfrom10.60.0to10.65.0inpackage.json. - Updates
package-lock.jsonto reflect the new@sentry/angularversion and related transitive dependency graph changes.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Upgrades @sentry/angular to 10.65.0. |
| package-lock.json | Updates lockfile for the Sentry Angular bump, including new transitive entries and metadata changes. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@sentry/angular": "10.65.0", | ||
| "@sentry/capacitor": "^4.2.0", |
Snyk has created this PR to upgrade @sentry/angular from 10.60.0 to 10.65.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 5 versions ahead of your current version.
The recommended version was released a month ago.
Breaking Change Risk
Release notes
Package name: @sentry/angular
urlattributes on pageload and navigation spans (#21985)url.templateon pageload spans (#22011)url.pathandurl.fullon pageload and navigation spans (#21952)attributesonSerializedStreamedSpan(#22052)url.template,url.pathandurl.fullon router spans (#22095)urlattributes on pageload and navigation spans (#22006)url.template,url.pathandurl.fullon routing spans (#22087)url.template,url.pathandurl.fullon pageload and navigation spans (#22018)url.templateon pageload and navigation spans (#22025)urlattributes on solid router and tanstack router spans (#22090)url.template,url.pathandurl.fullon pageload and navigation spans (#22027)url.templateand URL attributes on router spans (#22063)sentry.segment.nameattribute (#22024)'sentry.origin': manualwhen backfilling OTel data (#22102)Internal Changes
@ opentelemetry/instrumentation-graphqlto orchestrion (#21885)@ opentelemetry/instrumentation-redisto orchestrion (#21925)urlattribute creation (#22091)== nullchecks for nullish detection (#22154)attributesonSerializedStreamedSpanobjects (#22060)Work in this release was contributed by @ martijnwalraven. Thank you for your contribution!
Bundle size 📦
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 📦
url.fullattribute to resource spans (#21846)extendIntegrationmethod (#21759)isTracingSuppressedto the async context strategy (#21785)fastifyIntegration(#21706)sentry.status.messageattribute (#21811)Internal Changes
fastifyIntegration(#21706)spanStreamingIntegrationsetup intoServerRuntimeClient(#21814)mysqlinstrumentation with orchestrion bundler plugin (#21782)Work in this release was contributed by @ suzunn. Thank you for your contribution!
Bundle size 📦