Skip to content

refactor(deps): update dependencies (non-major) #389

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.

Sign up for GitHub

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

Jump to bottom
Merged
renovate merged 1 commit into from
Oct 1, 2025
Merged

refactor(deps): update dependencies (non-major) #389

renovate merged 1 commit into from
Oct 1, 2025

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 1, 2025

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

This PR contains the following updates:

Package Change Age Confidence
@fontsource/lato (source) 5.2.6 -> 5.2.7 age confidence
@icons-pack/react-simple-icons (source) 13.5.0 -> 13.8.0 age confidence
@react-router/fs-routes (source) 7.6.3 -> 7.9.3 age confidence
@react-router/node (source) 7.6.3 -> 7.9.3 age confidence
lucide-react (source) 0.525.0 -> 0.544.0 age confidence
react (source) 19.1.0 -> 19.1.1 age confidence
react-dom (source) 19.1.0 -> 19.1.1 age confidence
react-router (source) 7.6.3 -> 7.9.3 age confidence

Release Notes

fontsource/font-files (@​fontsource/lato)

v5.2.7

Compare Source

icons-pack/react-simple-icons (@​icons-pack/react-simple-icons)

v13.8.0

Compare Source

Minor Changes

v13.7.0

Compare Source

Minor Changes

v13.6.0

Compare Source

Minor Changes
remix-run/react-router (@​react-router/fs-routes)

v7.9.3

Compare Source

Patch Changes
  • Updated dependencies:
    • @react-router/dev@7.9.3

v7.9.2

Compare Source

Patch Changes
  • Updated dependencies:
    • @react-router/dev@7.9.2

v7.9.1

Compare Source

Patch Changes
  • Updated dependencies:
    • @react-router/dev@7.9.1

v7.9.0

Compare Source

Patch Changes
  • Updated dependencies:
    • @react-router/dev@7.9.0

v7.8.2

Compare Source

Patch Changes
  • Updated dependencies:
    • @react-router/dev@7.8.2

v7.8.1

Compare Source

Patch Changes
  • Updated dependencies:
    • @react-router/dev@7.8.1

v7.8.0

Compare Source

Patch Changes
  • Updated dependencies:
    • @react-router/dev@7.8.0

v7.7.1

Compare Source

Patch Changes
  • Updated dependencies:
    • @react-router/dev@7.7.1

v7.7.0

Compare Source

Patch Changes
  • Updated dependencies:
    • @react-router/dev@7.7.0
remix-run/react-router (@​react-router/node)

v7.9.3

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.9.3

v7.9.2

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.9.2

v7.9.1

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.9.1

v7.9.0

Compare Source

Minor Changes
Patch Changes
  • Updated dependencies:
    • react-router@7.9.0

v7.8.2

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.8.2

v7.8.1

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.8.1

v7.8.0

Compare Source

Patch Changes

  • [UNSTABLE] Change getLoadContext signature (type GetLoadContextFunction) when future.unstable_middleware is enabled so that it returns an unstable_RouterContextProvider instance instead of a Map used to contruct the instance internally (#​14097)

    • This also removes the type unstable_InitialContext export
    • ⚠️ This is a breaking change if you have adopted middleware and are using a custom server with a getLoadContext function

  • Updated dependencies:

    • react-router@7.8.0

v7.7.1

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.7.1

v7.7.0

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.7.0
lucide-icons/lucide (lucide-react)

v0.544.0: Version 0.544.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.543.0...0.544.0

v0.543.0: Version 0.543.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.542.0...0.543.0

v0.542.0: Version 0.542.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.541.0...0.542.0

v0.541.0: Version 0.541.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.540.0...0.541.0

v0.540.0: Version 0.540.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.539.0...0.540.0

v0.539.0: Version 0.539.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.538.0...0.539.0

v0.538.0: Version 0.538.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.537.0...0.538.0

v0.537.0: Version 0.537.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.536.0...0.537.0

v0.536.0: Version 0.536.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.535.0...0.536.0

v0.535.0: Version 0.535.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.534.0...0.535.0

v0.534.0: Version 0.534.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.533.0...0.534.0

v0.533.0: Version 0.533.0

Compare Source

What's Changed
New Contributors

Full Changelog: lucide-icons/lucide@0.532.0...0.533.0

v0.532.0: Version 0.532.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.531.0...0.532.0

v0.531.0: Version 0.531.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.530.0...0.531.0

v0.530.0: Version 0.530.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.529.0...0.530.0

v0.529.0: Version 0.529.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.528.0...0.529.0

v0.528.0: Version 0.528.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.527.0...0.528.0

v0.527.0: Version 0.527.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.526.0...0.527.0

v0.526.0: Version 0.526.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.525.0...0.526.0

facebook/react (react)

v19.1.1

Compare Source

facebook/react (react-dom)

v19.1.1

Compare Source

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

v7.9.3

Compare Source

Patch Changes

  • Do not try to use turbo-stream to decode CDN errors that never reached the server (#​14385)

    • We used to do this but lost this check with the adoption of single fetch

  • Fix Data Mode regression causing a 404 during initial load in when middleware exists without any loader functions (#​14393)

v7.9.2

Compare Source

Patch Changes
    • Update client-side router to run client middleware on initial load even if no loaders exist (#​14348)
    • Update createRoutesStub to run route middleware
      • You will need to set the <RoutesStub future={{ v8_middleware: true }} /> flag to enable the proper context type

  • Update Lazy Route Discovery manifest requests to use a singular comma-separated paths query param instead of repeated p query params (#​14321)

    • This is because Cloudflare has a hard limit of 100 URL search param key/value pairs when used as a key for caching purposes
    • If more that 100 paths were included, the cache key would be incomplete and could produce false-positive cache hits

  • [UNSTABLE] Add fetcher.unstable_reset() API (#​14206)

  • Made useOutlet element reference have stable identity in-between route chages (#​13382)

  • feat: enable full transition support for the rsc router (#​14362)

  • In RSC Data Mode, handle SSR'd client errors and re-try in the browser (#​14342)

  • Support middleware prop on <Route> for usage with a data router via createRoutesFromElements (#​14357)

  • Handle encoded question mark and hash characters in ancestor splat routes (#​14249)

  • Fail gracefully on manifest version mismatch logic if sessionStorage access is blocked (#​14335)

v7.9.1

Compare Source

Patch Changes
  • Fix internal Future interface naming from middleware -> v8_middleware (#​14327)

v7.9.0

Compare Source

Minor Changes
Patch Changes
  • Escape HTML in meta() JSON-LD content (#​14316)
  • Add react-server Await component implementation (#​14261)
  • In RSC Data Mode when using a custom basename, fix hydration errors for routes that only have client loaders (#​14264)
  • Make href function available in a react-server context (#​14262)
  • decode each time getPayload() is called to allow for "in-context" decoding and hoisting of contextual assets (#​14248)
  • href() now correctly processes routes that have an extension after the parameter or are a single optional parameter. (#​13797)

v7.8.2

Compare Source

Patch Changes

  • [UNSTABLE] Remove Data Mode future.unstable_middleware flag from createBrowserRouter (#​14213)

    • This is only needed as a Framework Mode flag because of the route modules and the getLoadContext type behavior change
    • In Data Mode, it's an opt-in feature because it's just a new property on a route object, so there's no behavior changes that necessitate a flag

  • [UNSTABLE] Add <RouterProvider unstable_onError>/<HydratedRouter unstable_onError> prop for client side error reporting (#​14162)

  • server action revalidation opt out via $SKIP_REVALIDATION field (#​14154)

  • Properly escape interpolated param values in generatePath() (#​13530)

  • Maintain ReadonlyMap and ReadonlySet types in server response data. (#​13092)

  • [UNSTABLE] Delay serialization of .data redirects to 202 responses until after middleware chain (#​14205)

  • Fix TypeError if you throw from patchRoutesOnNavigation when no partial matches exist (#​14198)

  • Fix basename usage without a leading slash in data routers (#​11671)

  • [UNSTABLE] Update client middleware so it returns the data strategy results allowing for more advanced post-processing middleware (#​14151)

v7.8.1

Compare Source

Patch Changes
  • Fix usage of optional path segments in nested routes defined using absolute paths (#​14135)
  • Bubble client pre-next middleware error to the shallowest ancestor that needs to load, not strictly the shallowest ancestor with a loader (#​14150)
  • Fix optional static segment matching in matchPath (#​11813)
  • Fix prerendering when a basename is set with ssr:false (#​13791)
  • Provide isRouteErrorResponse utility in react-server environments (#​14166)
  • Propagate non-redirect Responses thrown from middleware to the error boundary on document/data requests (#​14182)
  • Handle meta and links Route Exports in RSC Data Mode (#​14136)
  • Properly convert returned/thrown data() values to Response instances via Response.json() in resource routes and middleware (#​14159, #​14181)

v7.8.0

Compare Source

Minor Changes
  • Add nonce prop to Links & PrefetchPageLinks (#​14048)
  • Add loaderData arguments/properties alongside existing data arguments/properties to provide consistency and clarity between loaderData and actionData across the board (#​14047)
    • Updated types: Route.MetaArgs, Route.MetaMatch, MetaArgs, MetaMatch, Route.ComponentProps.matches, UIMatch
    • @deprecated warnings have been added to the existing data properties to point users to new loaderData properties, in preparation for removing the data properties in a future major release
Patch Changes

  • Prevent "Did not find corresponding fetcher result" console error when navigating during a fetcher.submit revalidation (#​14114)

  • Bubble client-side middleware errors prior to next to the appropriate ancestor error boundary (#​14138)

  • Switch Lazy Route Discovery manifest URL generation to usea standalone URLSearchParams instance instead of URL.searchParams to avoid a major performance bottleneck in Chrome (#​14084)

  • Adjust internal RSC usage of React.use to avoid Webpack compilation errors when using React 18 (#​14113)

  • Remove dependency on @types/node in TypeScript declaration files (#​14059)

  • Fix types for UIMatch to reflect that the loaderData/data properties may be undefined (#​12206)

    • When an ErrorBoundary is being rendered, not all active matches will have loader data available, since it may have been their loader that threw to trigger the boundary
    • The UIMatch.data type was not correctly handing this and would always reflect the presence of data, leading to the unexpected runtime errors when an ErrorBoundary was rendered
    • ⚠️ This may cause some type errors to show up in your code for unguarded match.data accesses - you should properly guard for undefined values in those scenarios.
    // app/root.tsx
export function loader() {
  someFunctionThatThrows(); // ❌ Throws an Error
  return { title: "My Title" };
}

export function Layout({ children }: { children: React.ReactNode }) {
  let matches = useMatches();
  let rootMatch = matches[0] as UIMatch<Awaited<ReturnType<typeof loader>>>;
  //  ^ rootMatch.data is incorrectly typed here, so TypeScript does not
  //    complain if you do the following which throws an error at runtime:
  let { title } = rootMatch.data; // 💥

  return <html>...</html>;
}

  • [UNSTABLE] Ensure resource route errors go through handleError w/middleware enabled (#​14078)

  • [UNSTABLE] Propagate returned Response from server middleware if next wasn't called (#​14093)

  • [UNSTABLE] Allow server middlewares to return data() values which will be converted into a Response (#​14093)

  • [UNSTABLE] Update middleware error handling so that the next function never throws and instead handles any middleware errors at the proper ErrorBoundary and returns the Response up through the ancestor next function (#​14118)

  • [UNSTABLE] When middleware is enabled, make the context parameter read-only (via Readonly<unstable_RouterContextProvider>) so that TypeScript will not allow you to write arbitrary fields to it in loaders, actions, or middleware. (#​14097)

  • [UNSTABLE] Rename and alter the signature/functionality of the unstable_respond API in staticHandler.query/staticHandler.queryRoute (#​14103)

    • The API has been renamed to unstable_generateMiddlewareResponse for clarity
    • The main functional change is that instead of running the loaders/actions before calling unstable_respond and handing you the result, we now pass a query/queryRoute function as a parameter and you execute the loaders/actions inside your callback, giving you full access to pre-processing and error handling
    • The query version of the API now has a signature of (query: (r: Request) => Promise<StaticHandlerContext | Response>) => Promise<Response>
    • The queryRoute version of the API now has a signature of (queryRoute: (r: Request) => Promise<Response>) => Promise<Response>
    • This allows for more advanced usages such as running logic before/after calling query and direct error handling of errors thrown from query
    • ⚠️ This is a breaking change if y

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Oct 1, 2025
@renovate renovate bot enabled auto-merge (squash) October 1, 2025 08:00
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from a644f0c to f46b7b3 Compare October 1, 2025 08:00
@renovate renovate bot merged commit 8976bb7 into main Oct 1, 2025
1 check passed
@renovate renovate bot deleted the renovate/dependencies-non-major branch October 1, 2025 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant