-
Notifications
You must be signed in to change notification settings - Fork 1
Bump @sentry/react from 8.55.0 to 10.16.0 #65
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.16.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.16.0) --- updated-dependencies: - dependency-name: "@sentry/react" dependency-version: 10.16.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
🤖 Dependabot Metadata:
|
Needs ReviewI recommend reviewing this upgrade before merging because the jump from version 8.55.0 to 10.16.0 introduces 21 breaking changes including deprecated API removals, modified integration behaviors, and changes to core functionality. While the codebase doesn't currently use Sentry, the major version upgrade requires careful review to ensure future integration compatibility and understand the significant architectural changes in the SDK. What we checked
Dependency UsageNo direct usages found in your codebase. Changes@sentry/react has been upgraded with 5 security fixes addressing injection vulnerabilities in Next.js instrumentation and Redux integration, plus 21 breaking changes including removal of deprecated APIs, modified Prisma instrumentation requirements, and changes to RPC method wrapping behavior. The update includes 252 critical bug fixes spanning navigation span handling, resource timing improvements, OpenAI SDK compatibility, and enhanced error capture across multiple frameworks including Next.js, React Router, and SvelteKit.
View 1175 more changes
References (5)[1]: Deprecated logger functionality removed in version 10.0.0, breaking existing logging integrations (more) [2]: sentrySolidStartVite export removed in version 9.0.0, affecting framework integrations (more) [3]: recordDroppedEvent API changed to no longer accept event argument, requiring code updates (more) [4]: Vue/Nuxt component tracking behavior changed - no longer creates update spans by default (more) [5]: Sentry React dependency updated but no current usage found in codebase - major version changes need review for future integration dependabot-metadata-test/package.json Line 19 in 9617efa
fossabot analyzed this PR using dependency research. |
|
Superseded by #66. |
Bumps @sentry/react from 8.55.0 to 10.16.0.
Release notes
Sourced from
@sentry/react's releases.... (truncated)
Changelog
Sourced from
@sentry/react's changelog.... (truncated)
Commits
74c5213release: 10.16.070811c9Merge pull request #17807 from getsentry/prepare-release/10.16.055d8514meta(changelog): Update changelog for 10.16.0c94d2a9fix(browser): Use current start timestamp for CLS span when CLS is 0 (#17800)5ce4435fix(nextjs): Don't use chalk in turbopack config file (#17806)22f8e5afix(react): Do not send additional navigation span on pageload (#17799)0b4a7b1chore: Addpublish_releasecommand (#17797)0e19673ref(core): Improve promise buffer (#17788)80d5ff2feat(logs): Add internalreplay_is_bufferingflag (#17752)8424fdctest(nextjs): Add route handler tests for turbopack (#17515)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)