HBASE-30203 Bump react-router from 7.12.0 to 7.15.0 in /hbase-website

[dependabot]

Bumps react-router from 7.12.0 to 7.15.0.

Release notes

Sourced from react-router's releases.

v7.15.0

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v7150

v7.14.2

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v7142

v7.14.1

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v7141

v7.14.0

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v7140

v7.13.2

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v7132

v7.13.1

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v7131

v7.13.0

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v7130

Changelog

Sourced from react-router's changelog.

v7.15.0

Minor Changes

• Stabilize unstable_defaultShouldRevalidate as defaultShouldRevalidate on <Link>, <Form>, useLinkClickHandler, useSubmit, fetcher.submit, and setSearchParams (a993f09)

  • ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly

• Stabilize the instrumentation APIs. unstable_instrumentations is now instrumentations and unstable_pattern is now pattern (a993f09)

  • The unstable_ServerInstrumentation, unstable_ClientInstrumentation, unstable_InstrumentRequestHandlerFunction, unstable_InstrumentRouterFunction, unstable_InstrumentRouteFunction, and unstable_InstrumentationHandlerResult types have had their unstable_ prefixes removed
  • ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly

• Stabilize unstable_mask as mask on <Link>, useLinkClickHandler, and useNavigate, and rename the corresponding Location.unstable_mask field to Location.mask (a993f09)

  • ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly

• Stabilize the unstable_normalizePath option on staticHandler.query and staticHandler.queryRoute as normalizePath (a993f09)

  • ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly

• Stabilize future.unstable_passThroughRequests as future.v8_passThroughRequests (a993f09)

  • ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly

• Remove unstable_subResourceIntegrity from the runtime FutureConfig type; the flag is now controlled by the top-level subResourceIntegrity option in react-router.config.ts (a993f09)

  • ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly

• Stabilize unstable_url as url on loader, action, and middleware function args (a993f09)

  • ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly

• Stabilize unstable_useTransitions as useTransitions on <BrowserRouter>, <HashRouter>, <HistoryRouter>, <MemoryRouter>, <Router>, <RouterProvider>, <HydratedRouter>, and useLinkClickHandler (a993f09)

  • ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly

Patch Changes

• Add nonce to <Scripts> <link rel="modulepreload"> elements (if provided) (af5d49b)

• Fix a bug with unstable_defaultShouldRevalidate={false} where parent routes that did not export a shouldRevalidate function could be incorrectly included in the single fetch call for new child route data (#15012)

• Improve server-side route matching performance by pre-computing flattened/cached route branches (#14967) (af5d49b)

  • Performance benchmarks showed roughly a 10-15% improvement in server-side request handling performance

• Mark mask as an optional field in Location for easier mocking in unit tests (#14999)

• Cache flattened/ranked route branches to optimize server-side route matching (#14967)

• Improve route matching performance in Framework/Data Mode (#14971) (af5d49b)

  • Avoiding unnecessary calls to matchRoutes in data router scenarios
    • This includes adding back the optimization that was removed in 7.6.0 (#13562)
    • The issues that prompted the revert have been addressed by using the available router matches but always updating match.route to the latest route in the manifest
  • Leverage pre-computed pre-computing flattened/cached route branches during client side route matching
  • Performance benchmarks showed roughly a 15-30% improvement in server-side request handling performance

v7.14.2

... (truncated)

Commits

• 97c8de7 Release v7.15.0 (#15018)
• af5d49b Update change files again
• a993f09 Update change files
• 362635b Move chnageset to change file
• e756132 chore: format
• 49295b5 Stabilize APIs (#14999)
• 5f61543 Client-side route matching optimizations (#14971)
• 67518cb Remove unnecessary hasShouldRevalidate condition for opting out (#15012)
• 6f18edd Add nonce to scripts modulepreload (#15002)
• 10a9686 Migrate changeset to change file
• Additional commits viewable in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[PDavid]

Unfortunately site cannot be built with this change, there is a huge error in the site build log:

[INFO] Running 'npm install' in /home/ws1test3/projects/upstream/hbase/hbase-website
[INFO] npm error code ERESOLVE
[INFO] npm error ERESOLVE could not resolve
[INFO] npm error
[INFO] npm error While resolving: @react-router/node@7.16.0
[INFO] npm error Found: react-router@7.15.0
[INFO] npm error node_modules/react-router
[INFO] npm error   react-router@"^7.15.0" from the root project
[INFO] npm error   peer react-router@"^7.12.0" from @react-router/dev@7.12.0
[INFO] npm error   node_modules/@react-router/dev
[INFO] npm error     dev @react-router/dev@"^7.12.0" from the root project
[INFO] npm error   1 more (fumadocs-core)
[INFO] npm error
[INFO] npm error Could not resolve dependency:
[INFO] npm error peer react-router@"7.16.0" from @react-router/node@7.16.0
[INFO] npm error node_modules/@react-router/node
[INFO] npm error   @react-router/node@"^7.12.0" from the root project
[INFO] npm error
[INFO] npm error Conflicting peer dependency: react-router@7.16.0
[INFO] npm error node_modules/react-router
[INFO] npm error   peer react-router@"7.16.0" from @react-router/node@7.16.0
[INFO] npm error   node_modules/@react-router/node
[INFO] npm error     @react-router/node@"^7.12.0" from the root project
[INFO] npm error
[INFO] npm error Fix the upstream dependency conflict, or retry
[INFO] npm error this command with --force or --legacy-peer-deps
[INFO] npm error to accept an incorrect (and potentially broken) dependency resolution.
[INFO] npm error
[INFO] npm error
[INFO] npm error For a full report see:
[INFO] npm error /home/ws1test3/.npm/_logs/2026-06-04T07_09_32_374Z-eresolve-report.txt
[INFO] npm notice
[INFO] npm notice New minor version of npm available! 11.6.2 -> 11.16.0
[INFO] npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.16.0
[INFO] npm notice To update run: npm install -g npm@11.16.0
[INFO] npm notice
[INFO] npm error A complete log of this run can be found in: /home/ws1test3/.npm/_logs/2026-06-04T07_09_32_374Z-debug-0.log
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

[PDavid]

I used Claude Code to fix this:

The issue is that @react-router/node@7.16.0 requires react-router@7.16.0 as an exact peer, but this branch only bumped react-router to 7.15.0.
The problem is clear. The dependabot PR bumped react-router to ^7.15.0 (line 69), but @react-router/node and @react-router/serve are on ^7.12.0 which resolves to 7.16.0 — and that version requires exactly react-router@7.16.0 as a peer. The fix is to update react-router to ^7.16.0 so all @react-router/* packages stay in sync.

Now the build is successful, website + docs looks good.

[liuxiaocs7]

Thanks @PDavid

[PDavid]

The build log now contains some (warnings?):

[INFO] > build
[INFO] > react-router build
[INFO] 
[INFO]   ⚠️  Future Flag Warning: Route middleware support is changing in React Router v8.
[INFO]      You can use the `future.v8_middleware` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_middleware
[INFO]   ⚠️  Future Flag Warning: Route module splitting behavior is changing in React Router v8.
[INFO]      You can use the `future.v8_splitRouteModules` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_splitRouteModules
[INFO]   ⚠️  Future Flag Warning: Vite Environment API usage is changing in React Router v8.
[INFO]      You can use the `future.v8_viteEnvironmentApi` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_viteEnvironmentApi
[INFO]   ⚠️  Future Flag Warning: Request handling behavior is changing in React Router v8.
[INFO]      You can use the `future.v8_passThroughRequests` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_passThroughRequests
[INFO]   ⚠️  Future Flag Warning: Data request URL formats are changing in React Router v8.
[INFO]      You can use the `future.v8_trailingSlashAwareDataRequests` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_trailingSlashAwareDataRequests
[INFO]   ⚠️  Future Flag Warning: Route middleware support is changing in React Router v8.
[INFO]      You can use the `future.v8_middleware` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_middleware
[INFO]   ⚠️  Future Flag Warning: Route module splitting behavior is changing in React Router v8.
[INFO]      You can use the `future.v8_splitRouteModules` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_splitRouteModules
[INFO]   ⚠️  Future Flag Warning: Vite Environment API usage is changing in React Router v8.
[INFO]      You can use the `future.v8_viteEnvironmentApi` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_viteEnvironmentApi
[INFO]   ⚠️  Future Flag Warning: Request handling behavior is changing in React Router v8.
[INFO]      You can use the `future.v8_passThroughRequests` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_passThroughRequests
[INFO]   ⚠️  Future Flag Warning: Data request URL formats are changing in React Router v8.
[INFO]      You can use the `future.v8_trailingSlashAwareDataRequests` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_trailingSlashAwareDataRequests
[INFO]   ⚠️  Future Flag Warning: Route middleware support is changing in React Router v8.
[INFO]      You can use the `future.v8_middleware` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_middleware
[INFO]   ⚠️  Future Flag Warning: Route module splitting behavior is changing in React Router v8.
[INFO]      You can use the `future.v8_splitRouteModules` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_splitRouteModules
[INFO]   ⚠️  Future Flag Warning: Vite Environment API usage is changing in React Router v8.
[INFO]      You can use the `future.v8_viteEnvironmentApi` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_viteEnvironmentApi
[INFO]   ⚠️  Future Flag Warning: Request handling behavior is changing in React Router v8.
[INFO]      You can use the `future.v8_passThroughRequests` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_passThroughRequests
[INFO]   ⚠️  Future Flag Warning: Data request URL formats are changing in React Router v8.
[INFO]      You can use the `future.v8_trailingSlashAwareDataRequests` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_trailingSlashAwareDataRequests
[INFO]   ⚠️  Future Flag Warning: Route middleware support is changing in React Router v8.
[INFO]      You can use the `future.v8_middleware` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_middleware
[INFO]   ⚠️  Future Flag Warning: Route module splitting behavior is changing in React Router v8.
[INFO]      You can use the `future.v8_splitRouteModules` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_splitRouteModules
[INFO]   ⚠️  Future Flag Warning: Vite Environment API usage is changing in React Router v8.
[INFO]      You can use the `future.v8_viteEnvironmentApi` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_viteEnvironmentApi
[INFO]   ⚠️  Future Flag Warning: Request handling behavior is changing in React Router v8.
[INFO]      You can use the `future.v8_passThroughRequests` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_passThroughRequests
[INFO]   ⚠️  Future Flag Warning: Data request URL formats are changing in React Router v8.
[INFO]      You can use the `future.v8_trailingSlashAwareDataRequests` flag to opt in early.
[INFO]      -> https://reactrouter.com/upgrading/future-flags#v8_trailingSlashAwareDataRequests
[INFO] [MDX] generated files in 0.6937669999999798ms

Can you maybe check if we should do something about these @yuriipalam?

[PDavid]

LGTM. Let's wait a bit for the review of @yuriipalam

[PDavid]

Regarding the above buld warnings Claude Code wrote:

These are opt-in flags that let you adopt React Router v8 breaking changes incrementally while still on v7. When v8 ships, these behaviors become the default. Here's what each one does:

• v8_middleware — Changes how route middleware (loaders/actions interceptors) works. New API for middleware chaining.
• v8_splitRouteModules — Route modules get code-split more aggressively (loader, action, component split into separate chunks instead of one bundle per route).
• v8_viteEnvironmentApi — Switches the dev server to use Vite's newer Environment API internally (affects how SSR/client builds are coordinated).
• v8_passThroughRequests — Unmatched requests pass through to the underlying server instead of returning a 404 from React Router.
• v8_trailingSlashAwareDataRequests — Data request URLs (used for client-side navigations) respect trailing slash settings rather than using a fixed format.

Since this project uses ssr: false (SPA mode), most of these are low-risk — v8_middleware, v8_passThroughRequests, and v8_viteEnvironmentApi primarily affect server-side behavior. The v8_splitRouteModules one could change bundle output, and v8_trailingSlashAwareDataRequests could affect
prerendered data URLs.