-
Notifications
You must be signed in to change notification settings - Fork 1
Bump @sentry/react from 8.55.0 to 10.18.0 #68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Bumps [@sentry/react](https://github.com/getsentry/sentry-javascript) from 8.55.0 to 10.18.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.18.0) --- updated-dependencies: - dependency-name: "@sentry/react" dependency-version: 10.18.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
✓ Safe to upgradeI recommend merging this upgrade because the @sentry/react package is declared but completely unused in the codebase. Despite this being a major version jump (8.x to 10.x) with significant breaking changes including ErrorBoundary API modifications, OpenTelemetry v2 integration, and IP address collection behavior changes, none of these affect the application since Sentry is not initialized or imported anywhere. The upgrade includes 342 new features and 259 bug fixes, and when the team eventually integrates error monitoring, they will benefit from the latest stable version with improved OpenTelemetry support and security fixes. What we checked
Dependency UsageThe @sentry/react package is declared as a dependency but remains completely unused throughout the codebase—no imports, initialization, or error tracking implementation exists in any React components or application entry points. This represents an orphaned dependency that was likely added for planned error monitoring and crash reporting functionality but never integrated into the CRUD application's user management interface or API layer. ChangesDependency Update Analysis@sentry/react UpgradeCritical security fixes address injection vulnerabilities in Next.js, Nuxt, and Redux integrations. The update includes 20 breaking changes primarily affecting instrumentation hooks (now deprecated in favor of
View 1200 more changes
References (5)[1]: @sentry/react declared as dependency but grep search confirms zero imports or usage across entire codebase dependabot-metadata-test/package.json Line 19 in d418b11
[2]: Main React entry point has no Sentry initialization - only imports React and ReactDOM
[3]: App component has no ErrorBoundary wrapper or Sentry imports - uses standard React error handling
[4]: Official migration guide documents breaking changes including ErrorBoundary componentStack type change (string instead of string | null | undefined), but these are irrelevant since Sentry is not used (source link) [5]: v9 to v10 migration introduces OpenTelemetry v2 upgrade and requires explicit sendDefaultPii: true for IP address collection, but package remains unused so no migration needed (source link) fossabot analyzed this PR using dependency research. |
🤖 Dependabot Metadata:
|
|
Hello 1 |
|
Test 1 |
|
Superseded by #70. |
Bumps @sentry/react from 8.55.0 to 10.18.0.
Release notes
Sourced from
@sentry/react's releases.... (truncated)
Changelog
Sourced from
@sentry/react's changelog.... (truncated)
Commits
716ec31release: 10.18.091961d9Merge pull request #17874 from getsentry/prepare-release/10.18.09ee2045meta(changelog): Update changelog for 10.18.09b584f2fix(react-router): Fix type forOriginalHandleRequestwith middleware (#17870)a524022chore: Add external contributor to CHANGELOG.md (#17866)2dbcfedfeat(core): Rename vercelai.schema to gen_ai.request.schema (#17850)a266909fix(nestjs): Add support for Symbol as event name (#17785)632f0b9feat: Remove@sentry/pino-transportpackage (#17851)e88c084feat(node):pinointegration (#17584)51a9deffix(core): Keep all property values in baggage header (#17847)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)