fix(deps): update dependency react-router-dom to v7.18.1 #65

Open
renovate-bot wants to merge 1 commit from renovate/react-router-monorepo into main
Contributor

This PR contains the following updates:

Package Change Age Confidence
react-router-dom (source) 7.15.07.18.1 age confidence

Release Notes

remix-run/react-router (react-router-dom)

v7.18.1

Compare Source

v7.18.0

Compare Source

Date: 2026-06-16

What's Changed
CSRF Check Logic Fix

We made a bug fix in our underlying CSRF checks in this release that may be a "breaking bug fix" for some users deployed behind a reverse proxy. The CSRF check now checks directly against the host in the request url provided, instead of looking directly at HTTP headers which is an adapter concern. If your adapter is not setting the expected host in the request URL, you may need to add the new internal host to your allowedActionOrigins config. This is most likely to occur in @react-router/serve apps or @react-router/express apps without the trust proxy setting enabled. We recommend testing this against application mutation requests as part of your upgrade.

Minor Changes
  • @react-router/architect - Add a useRequestContextDomainName option to createRequestHandler to derive request URL hosts from the API Gateway request context (#​15185)
    • This flag will become the default behavior in v8, so it is recommended to adopt to prepare for and to v8 better align with your deployment architecture and rely less on manual header parsing in the adapter
    • See the docs for more information
Patch Changes
  • react-router - Fix server handler prerender responses when using ssr: false and future.v8_trailingSlashAwareDataRequests: true (#​15173)
    • Avoids false positive "SPA Mode" detection when serving prerendered paths
  • react-router - Use the ServerRouter nonce for nonce-aware SSR components when they don't provide their own value so strict CSP pages can load them (#​15170)
  • react-router - Use turbo-stream to serialize and deserialize Framework Mode hydration errors (#​15175)
  • react-router - Optimize route matching by extending precomputed route branches to include matchers (#​15186)
  • react-router - Use the constructed request URL host instead of header checks when validating action request origins in the CSRF check (#​15185)
  • react-router - Remove the un-documented custom error serialization logic from Data Mode SSR built-in hydration flows (#​15175)
  • react-router - Validate protocols in RSC render redirects (#​15177)
  • react-router - Consolidate url normalization logic and better handle mixed slashes (#​15176)
  • @react-router/dev - Pass Vite server.watch config to child compiler in development mode. (#​15178)
  • @react-router/dev - Ignore external Vite server environments in Framework Mode build hooks (#​14883)
    • When future.v8_viteEnvironmentApi is enabled, React Router previously treated any non-client Vite environment as its own server build
    • This caused issues with integrations like Nitro, where plugins can register additional environments
    • Framework Mode build hooks now ignore external server environments and only process the app's own server build
  • @react-router/express - Adjust express adapter host computation (#​15185)
    • read port from x-forwarded-host based on trust proxy setting
    • handle invalid hostname characters

Full Changelog: v7.17.0...v7.18.0

v7.17.0

Compare Source

Date: 2026-06-04

Minor Changes
  • react-router - Ship a subset of the official documentation inside the react-router package (#​15121)
    • Markdown docs are now available in node_modules/react-router/docs, letting AI coding agents and the React Router agent skills read official docs locally
    • Excludes auto-generated API docs (api/), community/ content, and tutorials (tutorials/)
Patch Changes
  • @react-router/dev - Fix future flag warning URLs and only log each future flag warning one time (#​15138)
Unstable Changes

⚠️ Unstable features are not recommended for production use

  • @react-router/dev - Prevent RSC route module server exports from being scanned by the client dependency optimizer when future.unstable_optimizeDeps is enabled. (#​15005)

Full Changelog: v7.16.0...v7.17.0

v7.16.0

Compare Source

Date: 2026-05-28

Minor Changes
  • react-router - Stabilize future.unstable_trailingSlashAwareDataRequests as future.v8_trailingSlashAwareDataRequests (#​15098)

  • @react-router/dev - Stabilize future.unstable_trailingSlashAwareDataRequests as future.v8_trailingSlashAwareDataRequests (#​15098)

    • The unstable flag is no longer supported and will error during config resolution
  • @react-router/dev - Log future flag warnings for upcoming React Router v8 flags (#​15029)

    • v8_middleware, v8_splitRouteModules, v8_viteEnvironmentApi, v8_passThroughRequests, v8_trailingSlashAwareDataRequests
Patch Changes
  • react-router - Disable manifest path when lazy route dicovery is disabled (#​15068)

  • react-router - Fix browser URL creation to use the configured history window instead of the global window. (#​15066)

    • Pass the history/router window through to createBrowserURLImpl so custom window contexts keep the correct URL origin.
  • react-router - Fix useNavigation() return type to preserve discriminated union across navigation states (#​15095)

  • react-router - Widen MetaDescriptor script:ld+json type from LdJsonObject to LdJsonObject | LdJsonObject[] to permit multiple JSON-LD schemas in a single <script type="application/ld+json"> tag emitted by <Meta /> (#​15082)

  • react-router-dom - Remove stale/invalid unpkg field from package.json. This was removed from other packages with the release of v7 but missed in the react-router-dom re-export package (#​15075)

  • @react-router/express - Ignore writes after Express responses close (#​15107)

    • Avoid surfacing client disconnects as adapter errors when the response stream has already been destroyed or ended.
  • @react-router/node - Honor Node writable backpressure in writeReadableStreamToWritable and writeAsyncIterableToWritable (#​15071)

    • Await 'drain' when writable.write() returns false instead of letting chunks accumulate in the writable's internal buffer.
    • Reject (rather than hang) if the writable errors or closes mid-stream.
  • @react-router/serve - Normalize assetsBuildDirectory path separators in react-router-serve so Windows-built server artifacts can serve /assets/* correctly when run on Linux. (#​14982)

Full Changelog: v7.15.1...v7.16.0

v7.15.1

Compare Source

Date: 2026-05-14

What's New
useRouterState (unstable)

Following our Less is More design goal, this release includes a new unstable_useRouterState() hook (Framework + Data Mode) that consolidates access to active and pending router states (RFC, Roadmap Issue).

This should allow you to consolidate usages of a bunch of different hooks which will likely be marked deprecated later on in v8 and potentially removed in an eventual v9:

let { active, pending } = unstable_useRouterState();

// Active is always populated with the current location
active.location; // replaces `useLocation()`
active.searchParams; // replaces `useSearchParams()[0]`
active.params; // replaces `useParams()`
active.matches; // replaces `useMatches()`
active.type; // replaces `useNavigationType()`

// Pending is only populated during a navigation
pending.location; // replaces `useNavigation().location`
pending.searchParams; // equivalent to `new URLSearchParams(useNavigation().search)`
pending.params; // Not directly accessible today
pending.matches; // Not directly accessible today
pending.type; // Not directly accessible today
pending.state; // replaces `useNavigation().state`
pending.formMethod; // replaces useNavigation().formMethod
pending.formAction; // replaces useNavigation().formAction
pending.formEncType; // replaces useNavigation().formEncType
pending.formData; // replaces useNavigation().formData
pending.json; // replaces useNavigation().json
pending.text; // replaces useNavigation().text
Patch Changes
  • react-router - Memoize useFetchers to return a stable identity and only change if fetchers changed (#​15028)
  • react-router - Update router to operate on fetcher Maps in an immutable manner to avoid delayed React renders from potentially reading an updated but not yet committed Map. This could result in brief flickers in some fetcher-driven optimistic UI scenarios (#​15028)
  • react-router - Fix serverLoader() returning stale SSR data when a client navigation aborts pending hydration before the hydration clientLoader resolves (#​15022)
  • react-router - Fix RouterProvider onError callback not being called for synchronous initial loader errors in SPA mode (#​15039) (#​14942)
  • react-router - Internal refactor to consolidate mutation request detection through shared utility (#​15033)
  • @react-router/dev - Fix basename conflicting with app directory name when Vite base is set (#​15027)
    • When the Vite base config and React Router basename both match the app directory name (e.g. base: "/app/", basename: "/app/"), Vite would strip the base prefix from server-build virtual module import paths, causing "Failed to load url /root.tsx" errors
    • The fix uses /@&#8203;fs/ absolute paths for those imports to bypass Vite's base-stripping logic
Unstable Changes

⚠️ Unstable features are not recommended for production use

  • react-router - Add a new unstable_useRouterState() hook that consolidates access to active and pending router states (RFC: #​12358) (#​15017)
    • Data/Framework/RSC only — throws when used without a data router

Full Changelog: v7.15.0...v7.15.1


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 9am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [react-router-dom](https://github.com/remix-run/react-router) ([source](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom)) | [`7.15.0` → `7.18.1`](https://renovatebot.com/diffs/npm/react-router-dom/7.15.0/7.18.1) | ![age](https://developer.mend.io/api/mc/badges/age/npm/react-router-dom/7.18.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/react-router-dom/7.15.0/7.18.1?slim=true) | --- ### Release Notes <details> <summary>remix-run/react-router (react-router-dom)</summary> ### [`v7.18.1`](https://github.com/remix-run/react-router/compare/react-router-dom@7.18.0...react-router-dom@7.18.1) [Compare Source](https://github.com/remix-run/react-router/compare/react-router-dom@7.18.0...react-router-dom@7.18.1) ### [`v7.18.0`](https://github.com/remix-run/react-router/blob/HEAD/CHANGELOG.md#v7180) [Compare Source](https://github.com/remix-run/react-router/compare/react-router-dom@7.17.0...react-router-dom@7.18.0) Date: 2026-06-16 ##### What's Changed ##### CSRF Check Logic Fix We made a bug fix in our underlying CSRF checks in this release that may be a "breaking bug fix" for some users deployed behind a reverse proxy. The CSRF check now checks directly against the `host` in the `request` url provided, instead of looking directly at HTTP headers which is an adapter concern. If your adapter is not setting the expected host in the request URL, you may need to add the new internal host to your `allowedActionOrigins` config. This is most likely to occur in `@react-router/serve` apps or `@react-router/express` apps without the `trust proxy` setting enabled. We recommend testing this against application mutation requests as part of your upgrade. ##### Minor Changes - `@react-router/architect` - Add a `useRequestContextDomainName` option to `createRequestHandler` to derive request URL hosts from the API Gateway request context ([#&#8203;15185](https://github.com/remix-run/react-router/pull/15185)) - This flag will become the default behavior in v8, so it is recommended to adopt to prepare for and to v8 better align with your deployment architecture and rely less on manual header parsing in the adapter - See the [docs](https://reactrouter.com/api/other-api/adapter#react-routerarchitect) for more information ##### Patch Changes - `react-router` - Fix server handler prerender responses when using `ssr: false` and `future.v8_trailingSlashAwareDataRequests: true` ([#&#8203;15173](https://github.com/remix-run/react-router/pull/15173)) - Avoids false positive "SPA Mode" detection when serving prerendered paths - `react-router` - Use the `ServerRouter` `nonce` for nonce-aware SSR components when they don't provide their own value so strict CSP pages can load them ([#&#8203;15170](https://github.com/remix-run/react-router/pull/15170)) - `react-router` - Use `turbo-stream` to serialize and deserialize Framework Mode hydration errors ([#&#8203;15175](https://github.com/remix-run/react-router/pull/15175)) - `react-router` - Optimize route matching by extending precomputed route branches to include matchers ([#&#8203;15186](https://github.com/remix-run/react-router/pull/15186)) - `react-router` - Use the constructed `request` URL `host` instead of header checks when validating action request origins in the CSRF check ([#&#8203;15185](https://github.com/remix-run/react-router/pull/15185)) - `react-router` - Remove the un-documented custom error serialization logic from Data Mode SSR built-in hydration flows ([#&#8203;15175](https://github.com/remix-run/react-router/pull/15175)) - `react-router` - Validate protocols in RSC render redirects ([#&#8203;15177](https://github.com/remix-run/react-router/pull/15177)) - `react-router` - Consolidate url normalization logic and better handle mixed slashes ([#&#8203;15176](https://github.com/remix-run/react-router/pull/15176)) - `@react-router/dev` - Pass Vite `server.watch` config to child compiler in development mode. ([#&#8203;15178](https://github.com/remix-run/react-router/pull/15178)) - `@react-router/dev` - Ignore external Vite server environments in Framework Mode build hooks ([#&#8203;14883](https://github.com/remix-run/react-router/pull/14883)) - When `future.v8_viteEnvironmentApi` is enabled, React Router previously treated any non-client Vite environment as its own server build - This caused issues with integrations like Nitro, where plugins can register additional environments - Framework Mode build hooks now ignore external server environments and only process the app's own server build - `@react-router/express` - Adjust express adapter host computation ([#&#8203;15185](https://github.com/remix-run/react-router/pull/15185)) - read port from `x-forwarded-host` based on `trust proxy` setting - handle invalid hostname characters **Full Changelog**: [`v7.17.0...v7.18.0`](https://github.com/remix-run/react-router/compare/react-router@7.17.0...react-router@7.18.0) ### [`v7.17.0`](https://github.com/remix-run/react-router/blob/HEAD/CHANGELOG.md#v7170) [Compare Source](https://github.com/remix-run/react-router/compare/react-router-dom@7.16.0...react-router-dom@7.17.0) Date: 2026-06-04 ##### Minor Changes - `react-router` - Ship a subset of the official documentation inside the `react-router` package ([#&#8203;15121](https://github.com/remix-run/react-router/pull/15121)) - Markdown docs are now available in `node_modules/react-router/docs`, letting AI coding agents and the React Router agent skills read official docs locally - Excludes auto-generated API docs (`api/`), `community/` content, and tutorials (`tutorials/`) ##### Patch Changes - `@react-router/dev` - Fix future flag warning URLs and only log each future flag warning one time ([#&#8203;15138](https://github.com/remix-run/react-router/pull/15138)) ##### Unstable Changes ⚠️ *[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use* - `@react-router/dev` - Prevent RSC route module server exports from being scanned by the client dependency optimizer when `future.unstable_optimizeDeps` is enabled. ([#&#8203;15005](https://github.com/remix-run/react-router/pull/15005)) **Full Changelog**: [`v7.16.0...v7.17.0`](https://github.com/remix-run/react-router/compare/react-router@7.16.0...react-router@7.17.0) ### [`v7.16.0`](https://github.com/remix-run/react-router/blob/HEAD/CHANGELOG.md#v7160) [Compare Source](https://github.com/remix-run/react-router/compare/react-router-dom@7.15.1...react-router-dom@7.16.0) Date: 2026-05-28 ##### Minor Changes - `react-router` - Stabilize `future.unstable_trailingSlashAwareDataRequests` as `future.v8_trailingSlashAwareDataRequests` ([#&#8203;15098](https://github.com/remix-run/react-router/pull/15098)) - `@react-router/dev` - Stabilize `future.unstable_trailingSlashAwareDataRequests` as `future.v8_trailingSlashAwareDataRequests` ([#&#8203;15098](https://github.com/remix-run/react-router/pull/15098)) - The unstable flag is no longer supported and will error during config resolution - `@react-router/dev` - Log future flag warnings for upcoming React Router v8 flags ([#&#8203;15029](https://github.com/remix-run/react-router/pull/15029)) - `v8_middleware`, `v8_splitRouteModules`, `v8_viteEnvironmentApi`, `v8_passThroughRequests`, `v8_trailingSlashAwareDataRequests` ##### Patch Changes - `react-router` - Disable manifest path when lazy route dicovery is disabled ([#&#8203;15068](https://github.com/remix-run/react-router/pull/15068)) - `react-router` - Fix browser URL creation to use the configured history window instead of the global window. ([#&#8203;15066](https://github.com/remix-run/react-router/pull/15066)) - Pass the history/router window through to `createBrowserURLImpl` so custom window contexts keep the correct URL origin. - `react-router` - Fix `useNavigation()` return type to preserve discriminated union across navigation states ([#&#8203;15095](https://github.com/remix-run/react-router/pull/15095)) - `react-router` - Widen `MetaDescriptor` `script:ld+json` type from `LdJsonObject` to `LdJsonObject | LdJsonObject[]` to permit multiple JSON-LD schemas in a single `<script type="application/ld+json">` tag emitted by `<Meta />` ([#&#8203;15082](https://github.com/remix-run/react-router/pull/15082)) - `react-router-dom` - Remove stale/invalid `unpkg` field from `package.json`. This was removed from other packages with the release of v7 but missed in the `react-router-dom` re-export package ([#&#8203;15075](https://github.com/remix-run/react-router/pull/15075)) - `@react-router/express` - Ignore writes after Express responses close ([#&#8203;15107](https://github.com/remix-run/react-router/pull/15107)) - Avoid surfacing client disconnects as adapter errors when the response stream has already been destroyed or ended. - `@react-router/node` - Honor Node writable backpressure in `writeReadableStreamToWritable` and `writeAsyncIterableToWritable` ([#&#8203;15071](https://github.com/remix-run/react-router/pull/15071)) - Await `'drain'` when `writable.write()` returns `false` instead of letting chunks accumulate in the writable's internal buffer. - Reject (rather than hang) if the writable errors or closes mid-stream. - `@react-router/serve` - Normalize `assetsBuildDirectory` path separators in `react-router-serve` so Windows-built server artifacts can serve `/assets/*` correctly when run on Linux. ([#&#8203;14982](https://github.com/remix-run/react-router/pull/14982)) **Full Changelog**: [`v7.15.1...v7.16.0`](https://github.com/remix-run/react-router/compare/react-router@7.15.1...react-router@7.16.0) ### [`v7.15.1`](https://github.com/remix-run/react-router/blob/HEAD/CHANGELOG.md#v7151) [Compare Source](https://github.com/remix-run/react-router/compare/react-router-dom@7.15.0...react-router-dom@7.15.1) Date: 2026-05-14 ##### What's New ##### `useRouterState` (unstable) Following our [Less is More](https://github.com/remix-run/react-router/blob/main/GOVERNANCE.md#design-goals) design goal, this release includes a new `unstable_useRouterState()` hook (Framework + Data Mode) that consolidates access to active and pending router states ([RFC](https://github.com/remix-run/react-router/discussions/12358), [Roadmap Issue](https://github.com/remix-run/react-router/issues/13073)). This should allow you to consolidate usages of a bunch of different hooks which will likely be marked deprecated later on in v8 and potentially removed in an eventual v9: ```ts let { active, pending } = unstable_useRouterState(); // Active is always populated with the current location active.location; // replaces `useLocation()` active.searchParams; // replaces `useSearchParams()[0]` active.params; // replaces `useParams()` active.matches; // replaces `useMatches()` active.type; // replaces `useNavigationType()` // Pending is only populated during a navigation pending.location; // replaces `useNavigation().location` pending.searchParams; // equivalent to `new URLSearchParams(useNavigation().search)` pending.params; // Not directly accessible today pending.matches; // Not directly accessible today pending.type; // Not directly accessible today pending.state; // replaces `useNavigation().state` pending.formMethod; // replaces useNavigation().formMethod pending.formAction; // replaces useNavigation().formAction pending.formEncType; // replaces useNavigation().formEncType pending.formData; // replaces useNavigation().formData pending.json; // replaces useNavigation().json pending.text; // replaces useNavigation().text ``` ##### Patch Changes - `react-router` - Memoize `useFetchers` to return a stable identity and only change if fetchers changed ([#&#8203;15028](https://github.com/remix-run/react-router/pull/15028)) - `react-router` - Update router to operate on fetcher Maps in an immutable manner to avoid delayed React renders from potentially reading an updated but not yet committed Map. This could result in brief flickers in some fetcher-driven optimistic UI scenarios ([#&#8203;15028](https://github.com/remix-run/react-router/pull/15028)) - `react-router` - Fix `serverLoader()` returning stale SSR data when a client navigation aborts pending hydration before the hydration `clientLoader` resolves ([#&#8203;15022](https://github.com/remix-run/react-router/pull/15022)) - `react-router` - Fix `RouterProvider` `onError` callback not being called for synchronous initial loader errors in SPA mode ([#&#8203;15039](https://github.com/remix-run/react-router/pull/15039)) ([#&#8203;14942](https://github.com/remix-run/react-router/pull/14942)) - `react-router` - Internal refactor to consolidate mutation request detection through shared utility ([#&#8203;15033](https://github.com/remix-run/react-router/pull/15033)) - `@react-router/dev` - Fix `basename` conflicting with `app` directory name when Vite `base` is set ([#&#8203;15027](https://github.com/remix-run/react-router/pull/15027)) - When the Vite `base` config and React Router `basename` both match the app directory name (e.g. `base: "/app/"`, `basename: "/app/"`), Vite would strip the base prefix from server-build virtual module import paths, causing "Failed to load url /root.tsx" errors - The fix uses `/@&#8203;fs/` absolute paths for those imports to bypass Vite's base-stripping logic ##### Unstable Changes ⚠️ *[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use* - `react-router` - Add a new `unstable_useRouterState()` hook that consolidates access to active and pending router states (RFC: [#&#8203;12358](https://github.com/remix-run/react-router/issues/12358)) ([#&#8203;15017](https://github.com/remix-run/react-router/pull/15017)) - Data/Framework/RSC only — throws when used without a data router **Full Changelog**: [`v7.15.0...v7.15.1`](https://github.com/remix-run/react-router/compare/react-router@7.15.0...react-router@7.15.1) </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - "before 9am on monday" - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNDkuNSIsInVwZGF0ZWRJblZlciI6IjQzLjI0OS41IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
fix(deps): update dependency react-router-dom to v7.18.1
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 1s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m3s
CI / Backend lint (ruff) (pull_request) Successful in 34s
CI / Docker image build (pull_request) Successful in 39s
CI / Bot tests and audit (pull_request) Successful in 1m46s
d499f432ba
renovate-bot scheduled this pull request to auto merge when all checks succeed 2026-07-06 04:11:16 +00:00
renovate-bot force-pushed renovate/react-router-monorepo from d499f432ba
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 1s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m3s
CI / Backend lint (ruff) (pull_request) Successful in 34s
CI / Docker image build (pull_request) Successful in 39s
CI / Bot tests and audit (pull_request) Successful in 1m46s
to b721399275
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 1s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m3s
CI / Backend lint (ruff) (pull_request) Successful in 33s
CI / Docker image build (pull_request) Successful in 11s
CI / Bot tests and audit (pull_request) Successful in 1m40s
2026-07-06 05:10:07 +00:00
Compare
renovate-bot force-pushed renovate/react-router-monorepo from b721399275
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 1s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m3s
CI / Backend lint (ruff) (pull_request) Successful in 33s
CI / Docker image build (pull_request) Successful in 11s
CI / Bot tests and audit (pull_request) Successful in 1m40s
to eb1d3a8014
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 1s
CI / Backend lint (ruff) (pull_request) Successful in 31s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m8s
CI / Docker image build (pull_request) Successful in 11s
CI / Bot tests and audit (pull_request) Successful in 1m48s
2026-07-06 06:10:56 +00:00
Compare
renovate-bot force-pushed renovate/react-router-monorepo from eb1d3a8014
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 1s
CI / Backend lint (ruff) (pull_request) Successful in 31s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m8s
CI / Docker image build (pull_request) Successful in 11s
CI / Bot tests and audit (pull_request) Successful in 1m48s
to f6d0d3e91c
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 1s
CI / Frontend tests, audit, and build (pull_request) Successful in 55s
CI / Backend lint (ruff) (pull_request) Successful in 31s
CI / Docker image build (pull_request) Successful in 31s
CI / Bot tests and audit (pull_request) Successful in 1m39s
2026-07-06 07:11:10 +00:00
Compare
renovate-bot force-pushed renovate/react-router-monorepo from f6d0d3e91c
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 1s
CI / Frontend tests, audit, and build (pull_request) Successful in 55s
CI / Backend lint (ruff) (pull_request) Successful in 31s
CI / Docker image build (pull_request) Successful in 31s
CI / Bot tests and audit (pull_request) Successful in 1m39s
to 997cd8213a
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 1s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m3s
CI / Backend lint (ruff) (pull_request) Successful in 30s
CI / Docker image build (pull_request) Successful in 27s
CI / Bot tests and audit (pull_request) Successful in 1m42s
2026-07-06 08:10:42 +00:00
Compare
renovate-bot force-pushed renovate/react-router-monorepo from 997cd8213a
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 1s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m3s
CI / Backend lint (ruff) (pull_request) Successful in 30s
CI / Docker image build (pull_request) Successful in 27s
CI / Bot tests and audit (pull_request) Successful in 1m42s
to 49395e0274
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 1s
CI / Backend lint (ruff) (pull_request) Successful in 30s
CI / Frontend tests, audit, and build (pull_request) Successful in 54s
CI / Docker image build (pull_request) Successful in 9s
CI / Bot tests and audit (pull_request) Successful in 1m34s
2026-07-06 09:10:52 +00:00
Compare
renovate-bot force-pushed renovate/react-router-monorepo from 49395e0274
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 1s
CI / Backend lint (ruff) (pull_request) Successful in 30s
CI / Frontend tests, audit, and build (pull_request) Successful in 54s
CI / Docker image build (pull_request) Successful in 9s
CI / Bot tests and audit (pull_request) Successful in 1m34s
to 30ced92acc
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 2s
CI / Backend lint (ruff) (pull_request) Successful in 44s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m7s
CI / Docker image build (pull_request) Successful in 9s
CI / Bot tests and audit (pull_request) Successful in 1m49s
2026-07-13 04:23:20 +00:00
Compare
renovate-bot force-pushed renovate/react-router-monorepo from 30ced92acc
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 2s
CI / Backend lint (ruff) (pull_request) Successful in 44s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m7s
CI / Docker image build (pull_request) Successful in 9s
CI / Bot tests and audit (pull_request) Successful in 1m49s
to c48437cece
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 2s
CI / Frontend tests, audit, and build (pull_request) Successful in 57s
CI / Backend lint (ruff) (pull_request) Successful in 39s
CI / Docker image build (pull_request) Successful in 38s
CI / Bot tests and audit (pull_request) Successful in 1m55s
2026-07-13 05:22:44 +00:00
Compare
renovate-bot force-pushed renovate/react-router-monorepo from c48437cece
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 2s
CI / Frontend tests, audit, and build (pull_request) Successful in 57s
CI / Backend lint (ruff) (pull_request) Successful in 39s
CI / Docker image build (pull_request) Successful in 38s
CI / Bot tests and audit (pull_request) Successful in 1m55s
to b4fe72d8a2
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 2s
CI / Backend lint (ruff) (pull_request) Successful in 37s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m12s
CI / Docker image build (pull_request) Successful in 34s
CI / Bot tests and audit (pull_request) Successful in 1m54s
2026-07-13 06:34:54 +00:00
Compare
renovate-bot force-pushed renovate/react-router-monorepo from b4fe72d8a2
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 2s
CI / Backend lint (ruff) (pull_request) Successful in 37s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m12s
CI / Docker image build (pull_request) Successful in 34s
CI / Bot tests and audit (pull_request) Successful in 1m54s
to 46063cbba9
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 2s
CI / Backend lint (ruff) (pull_request) Successful in 38s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m0s
CI / Docker image build (pull_request) Successful in 9s
CI / Bot tests and audit (pull_request) Successful in 1m47s
2026-07-13 09:21:55 +00:00
Compare
renovate-bot force-pushed renovate/react-router-monorepo from 46063cbba9
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 2s
CI / Backend lint (ruff) (pull_request) Successful in 38s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m0s
CI / Docker image build (pull_request) Successful in 9s
CI / Bot tests and audit (pull_request) Successful in 1m47s
to 5b7435c176
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 3s
CI / Backend lint (ruff) (pull_request) Successful in 46s
CI / Docker image build (pull_request) Successful in 35s
CI / Frontend tests, audit, and build (pull_request) Successful in 1m14s
CI / Bot tests and audit (pull_request) Successful in 2m1s
2026-07-13 10:22:18 +00:00
Compare
Some checks failed
CI / Backend migration, tests, and audit (pull_request) Failing after 3s
Required
Details
CI / Backend lint (ruff) (pull_request) Successful in 46s
Required
Details
CI / Docker image build (pull_request) Successful in 35s
Required
Details
CI / Frontend tests, audit, and build (pull_request) Successful in 1m14s
Required
Details
CI / Bot tests and audit (pull_request) Successful in 2m1s
Required
Details
Some required checks were not successful.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/react-router-monorepo:renovate/react-router-monorepo
git switch renovate/react-router-monorepo
Sign in to join this conversation.
No description provided.