chore(deps): bump react-router-dom from 6.30.3 to 7.14.2#114831
chore(deps): bump react-router-dom from 6.30.3 to 7.14.2#114831dependabot[bot] wants to merge 1 commit intomasterfrom
Conversation
Bumps [react-router-dom](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom) from 6.30.3 to 7.14.2. - [Release notes](https://github.com/remix-run/react-router/releases) - [Changelog](https://github.com/remix-run/react-router/blob/main/packages/react-router-dom/CHANGELOG.md) - [Commits](https://github.com/remix-run/react-router/commits/react-router-dom@7.14.2/packages/react-router-dom) --- updated-dependencies: - dependency-name: react-router-dom dependency-version: 7.14.2 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
github-actions
Bot
added
the
Scope: Frontend
📊 Type Coverage Diff✅ No new type safety issues introduced. Coverage: 93.40% |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 3 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit cdfd4e5. Configure here.
| "react-mentions": "4.4.10", | ||
| "react-popper": "^2.3.0", | ||
| "react-router-dom": "6.30.3", | ||
| "react-router-dom": "7.14.2", |
There was a problem hiding this comment.
nuqs adapter uses v6 path incompatible with v7
High Severity
Bumping react-router-dom to v7 without updating the nuqs adapter import path will break URL search params state management. static/app/main.tsx and static/gsAdmin/init.tsx both import from nuqs/adapters/react-router/v6, which is explicitly incompatible with React Router v7. The adapter needs to be changed to nuqs/adapters/react-router/v7.
Reviewed by Cursor Bugbot for commit cdfd4e5. Configure here.
| "react-mentions": "4.4.10", | ||
| "react-popper": "^2.3.0", | ||
| "react-router-dom": "6.30.3", | ||
| "react-router-dom": "7.14.2", |
There was a problem hiding this comment.
Sentry router wrapper uses v6-specific function with v7
High Severity
static/app/main.tsx and static/gsAdmin/init.tsx use wrapCreateBrowserRouterV6 from @sentry/react to instrument the router. With react-router-dom bumped to v7, this needs to be wrapCreateBrowserRouterV7. The v6 wrapper may not correctly instrument the v7 router object, breaking Sentry performance monitoring and transaction tracking.
Reviewed by Cursor Bugbot for commit cdfd4e5. Configure here.
| "react-mentions": "4.4.10", | ||
| "react-popper": "^2.3.0", | ||
| "react-router-dom": "6.30.3", | ||
| "react-router-dom": "7.14.2", |
There was a problem hiding this comment.
Sentry tracing integration targets wrong router version
Medium Severity
static/app/bootstrap/initializeSdk.tsx uses Sentry.reactRouterV6BrowserTracingIntegration for browser tracing. With react-router-dom bumped to v7, this needs to be Sentry.reactRouterV7BrowserTracingIntegration. While the underlying implementations are similar, using the wrong version-specific integration could result in incorrect route parameterization in traces.
Reviewed by Cursor Bugbot for commit cdfd4e5. Configure here.
Bumps react-router-dom from 6.30.3 to 7.14.2.
Release notes
Sourced from react-router-dom's releases.
Changelog
Sourced from react-router-dom's changelog.
... (truncated)
Commits
cf1d250Release v7.14.2 (#14993)197674bRelease 7.14.1 (#14973)a87774fAdd new release process (#14916)e31077bchore: Update version for release (#14945)6683e85chore: Update version for release (pre) (#14943)aadb56fchore: Update version for release (#14908)c68a9b3chore: Update version for release (pre) (#14893)aa3f078chore: Update version for release (#14829)3207a5cchore: Update version for release (pre) (#14814)5557ba3chore: Update version for release (#14749)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 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)