-
Notifications
You must be signed in to change notification settings - Fork 1
Bump @sentry/react from 8.55.0 to 10.17.0 #66
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.17.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.17.0) --- updated-dependencies: - dependency-name: "@sentry/react" dependency-version: 10.17.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 codebase does not actually use any Sentry functionality despite having it as a dependency. The package is declared in package.json but there are no imports, initialization code, or API calls to Sentry anywhere in the application. While the upgrade spans a major version jump with 19 breaking changes, 5 security fixes, and 21 deprecations affecting features like Prisma instrumentation, Redux integration, logger APIs, and various SDK-specific integrations, none of these impact this project since Sentry is not integrated into the code. The upgrade can proceed safely without any code changes required. What we checked
Dependency UsageNo direct usages found in your codebase. ChangesUpdated @sentry/react with 5 security fixes addressing injection vulnerabilities in Next.js, Redux, Turbopack, and Nuxt configurations. Contains 19 breaking changes including removal of Prisma instrumentation dependency requirements, deprecated OpenTelemetry HTTP instrumentation, and changes to Fastify error handling and request isolation patterns.
View 1174 more changes
References (6)[1]: @sentry/react is listed as a dependency but is not imported or used anywhere in the codebase dependabot-metadata-test/package.json Line 19 in db5ccde
[2]: No Sentry imports in main React entry point - only React and ReactDOM imports present
[3]: No Sentry imports in main App component - no error boundary or performance monitoring configured
[4]: No Sentry imports in Express server entry point - no backend instrumentation present dependabot-metadata-test/src/index.ts Line 1 in db5ccde
[5]: Breaking change for Anthropic AI client instrumentation - not applicable as project doesn't use Anthropic or Sentry instrumentation (more) [6]: Major version upgrade includes 336 new features and 254 bug fixes, but project has no Sentry integration to benefit from or be affected by these changes (more) fossabot analyzed this PR using dependency research. |
🤖 Dependabot Metadata:
|
|
Superseded by #68. |
Bumps @sentry/react from 8.55.0 to 10.17.0.
Release notes
Sourced from
@sentry/react's releases.... (truncated)
Changelog
Sourced from
@sentry/react's changelog.... (truncated)
Commits
eb6e294release: 10.17.07dd3a82Merge pull request #17827 from getsentry/prepare-release/10.17.07b7ba0dmeta(changelog): Update changelog for 10.17.0264ad0bfeat(nuxt): Implement server middleware instrumentation (#17796)11ea830fix(aws-serverless): Takehttp_proxyinto account when choosing `useLayerEx...e966cdcdoc(core): Fix outdated JSDoc inbeforeSendSpan(#17815)7b40a95feat(node): Split up http integration into composable parts (#17524)4a9946cci: Do not run dependabot on e2e test applications (#17813)68a4eb3Merge pull request #17812 from getsentry/master559d8a5Merge branch 'release/10.16.0'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)