Bump @sentry/react from 8.55.0 to 10.21.0 #72
Closed
Conversation
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
Bumps [@sentry/react](https://github.com/getsentry/sentry-javascript) from 8.55.0 to 10.21.0. - [Release notes](https://github.com/getsentry/sentry-javascript/releases) - [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md) - [Commits](getsentry/sentry-javascript@8.55.0...10.21.0) --- updated-dependencies: - dependency-name: "@sentry/react" dependency-version: 10.21.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
|
|
✓ Safe to upgradeI recommend merging this upgrade because the package is currently installed but completely unused in the codebase - no Sentry initialization, error boundaries, or monitoring instrumentation exists. While this is a major version jump (v8 to v10) with 20 breaking changes, 6 security fixes, and 17 deprecations, none of these affect the project since @sentry/react is not imported or utilized anywhere. The upgrade eliminates the medium severity prototype pollution vulnerability (GHSA-593m-55hh-j8gv) and provides 318 new features and 271 bug fixes that will be available when Sentry monitoring is eventually implemented. What we checked
Dependency UsageThe @sentry/react dependency is declared in package.json but currently unused throughout the codebase. Despite being listed as a production dependency, no Sentry SDK initialization, error boundary components, or monitoring instrumentation has been implemented in the React frontend application. This represents an installed but inactive error tracking capability that is not yet contributing to application monitoring or user experience improvement. ChangesThe @sentry/react package was upgraded with 5 critical security fixes addressing injection vulnerabilities in Next.js, Nuxt, and React Redux integrations, and 20 breaking changes including removed Prisma instrumentation requirements, deprecated ANR integration, and elimination of manual Fastify error handler setup. Notable improvements include 271 bug fixes for frameworks like Next.js, Cloudflare Workers, and React Router, plus 318 new features spanning AI instrumentation (OpenAI, Vercel AI), enhanced Turbopack support, and improved trace propagation across async boundaries.
View 1165 more changes
References (6)[1]: @sentry/react declared as dependency but never imported or used in any React components dependabot-metadata-test/package.json Line 19 in a9ad5b6 [2]: Main React entry point contains no Sentry initialization code or imports [3]: Root application component has no Sentry ErrorBoundary or monitoring integration [4]: Migration guide documents breaking changes in integrations API and ErrorBoundary typing that would require updates when Sentry is eventually implemented (source link) [5]: v9 to v10 migration includes OpenTelemetry v2 upgrade with Web Vitals changes (FID to INP) - no current impact as monitoring is not active (source link) [6]: Automated codemod tool @sentry/migr8 available to handle upgrade changes when Sentry integration is implemented (source link) fossabot analyzed this PR using dependency research. |
🤖 Dependabot Metadata:
|
|
Superseded by #73. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/sentry/react-10.21.0
branch
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.
Bumps @sentry/react from 8.55.0 to 10.21.0.
Release notes
Sourced from
@sentry/react's releases.... (truncated)
Changelog
Sourced from
@sentry/react's changelog.... (truncated)
Commits
349a372release: 10.21.0300dce1Merge pull request #17984 from getsentry/prepare-release/10.21.05bc35a7meta(changelog): Update changelog for 10.21.040bcc3dfix(core): Improve uuid performance (#17938)75f68c7fix(core): Fix and add missing cache attributes in Vercel AI (#17982)d551d23feat(browserProfiling): Addtracelifecycle mode for UI profiling (#17619)1bd76c0fix(ember): Use updated version forclean-css(#17979)063ad99fix(nextjs): Don't set experimental instrumentation hook flag for next 16 (#1...910b40bfix(nextjs): Update bundler detection (#17976)f664505chore(build): Upgrade nodemon to 3.1.10 (#17956)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)