Skip to content

Update all patch and minor dependencies#28

Open
renovate-bot wants to merge 1 commit intosourcifyeth:stagingfrom
renovate-bot:renovate/all-patch-and-minor
Open

Update all patch and minor dependencies#28
renovate-bot wants to merge 1 commit intosourcifyeth:stagingfrom
renovate-bot:renovate/all-patch-and-minor

Conversation

@renovate-bot
Copy link
Copy Markdown
Contributor

@renovate-bot renovate-bot commented Mar 9, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
@ethereum-sourcify/compilers-types (source) 1.0.7 → 1.2.0 age confidence devDependencies minor
@ethereum-sourcify/lib-sourcify 2.3.0 → 2.3.1 age confidence dependencies patch
@headlessui/react (source) 2.2.4 → 2.2.10 age confidence dependencies patch
@react-router/dev (source) 7.6.2 → 7.14.1 age confidence devDependencies minor
@react-router/serve (source) 7.6.2 → 7.14.1 age confidence dependencies minor
@solidity-parser/parser 0.20.1 → 0.20.2 age confidence dependencies patch
@tailwindcss/vite (source) 4.1.10 → 4.2.2 age confidence devDependencies minor
@types/node (source) 20.19.1 → 20.19.39 age confidence devDependencies patch
@types/react (source) 19.1.8 → 19.2.14 age confidence devDependencies minor
@types/react-dom (source) 19.1.6 → 19.2.3 age confidence devDependencies minor
diff ^8.0.2 → 8.0.3 age confidence dependencies pin
ethers (source) 6.15.0 → 6.16.0 age confidence dependencies minor
fuse.js (source) 7.1.0 → 7.3.0 age confidence dependencies minor
isbot (source) 5.1.28 → 5.1.38 age confidence dependencies patch
react (source) 19.1.0 → 19.2.5 age confidence dependencies minor
react-dom (source) 19.1.0 → 19.2.5 age confidence dependencies minor
react-icons 5.5.0 → 5.6.0 age confidence dependencies minor
react-tooltip 5.29.1 → 5.30.1 age confidence dependencies minor
serve 14.2.5 → 14.2.6 age confidence dependencies patch
tailwindcss (source) 4.1.10 → 4.2.2 age confidence devDependencies minor
typescript (source) 5.8.3 → 5.9.3 age confidence devDependencies minor
vite (source) ^6.3.3 → 6.4.2 age confidence devDependencies pin

Release Notes

argotorg/sourcify (@​ethereum-sourcify/compilers-types)

v1.2.0

Compare Source

@​ethereum-sourcify/compilers-types@​1.2.0 - 2026-04-14

  • Add VyperStorageLayout type and capture missing Vyper compiler output fields (#​2739)

v1.1.0

Compare Source

@​ethereum-sourcify/compilers-types@​1.1.0 - 2026-03-30

  • feat: add Fe language support for smart contract verification (#​2692)

v1.0.13

Compare Source

@​ethereum-sourcify/compilers-types@​1.0.13 - 2026-03-17

  • Add TransientStorageLayout type (#​2689)
  • Refinements to SolidityOutputContract for supporting all Solidity versions (#​2652)

v1.0.12

Compare Source

@​ethereum-sourcify/compilers-types@​1.0.12 - 2026-03-02

  • improved types for StorageLayout and VyperSourceMap

v1.0.11

Compare Source

@​ethereum-sourcify/compilers-types@​1.0.11 - 2026-01-07

  • Add AnyJsonInput type

v1.0.10

Compare Source

@​ethereum-sourcify/compilers-types@​1.0.10 - 2025-10-28

none

v1.0.9

Compare Source

@​ethereum-sourcify/compilers-types@​1.0.9 - 2025-10-16

  • Update dependencies

v1.0.8

Compare Source

@​ethereum-sourcify/compilers-types@​1.0.8 - 2025-09-18

  • update repo links
tailwindlabs/headlessui (@​headlessui/react)

v2.2.10

Compare Source

Fixed
  • Don’t render <Portal> while hydrating (#​3825)
  • Fix passing props on Fragment error due to Symbol(react.lazy) (#​3873)

v2.2.9

Compare Source

Fixed
  • Improve focus management in shadow DOM roots (#​3794)
  • Don't accidentally open the Combobox when touching the ComboboxButton while dragging on mobile (#​3795)
  • Ensure sibling Dialog components are scrollable on mobile (#​3796)
  • Infer Combobox type based on onChange handler (#​3798)
  • Allow home/end key default behavior inside ComboboxInput when Combobox is closed (#​3798)
  • Ensure interacting with a Dialog on iOS works after interacting with a disallowed area (#​3801)
  • Freeze Listbox values as soon as a value is selected (#​3802)
  • Ensure refs are forwarded when freezing data (#​3390)
  • Do not serialize React components into form fields (49e9e8e)

v2.2.8

Compare Source

Fixed
  • Ensure we are not freezing data when the static prop is used (#​3779)
  • Ensure onChange types are contravariant instead of bivariant (#​3781)
  • Support <summary> as a focusable element inside <details> (#​3389)
  • Fix Maximum update depth exceeded crash when using transition prop (#​3782)
  • Ensure pressing Tab in the ComboboxInput, correctly syncs the input value (#​3785)
  • Ensure --button-width and --input-width have the latest value (#​3786)
  • Fix 'Invalid prop data-headlessui-state supplied to React.Fragment' warning (#​3788)
  • Ensure element in ref callback is always connected when rendering in a Portal (#​3789)
  • Ensure form state is up to date when using uncontrolled components (#​3790)
  • Ensure data-open on ComboboxInput is up to date (#​3791)
  • Ensure changing the immediate prop value on the Combobox component works as expected (#​3792)

v2.2.7

Compare Source

Fixed
  • Fix incorrect double invocation of menu items, listbox options and combobox options (#​3766)
  • Fix memory leak in SSR environment (#​3767)
  • Ensure programmatic .click() on MenuButton ref works (#​3768)
  • Don't activate hovered items while using the keyboard (#​3769)

v2.2.6

Compare Source

Fixed
  • Fix immediately closing Listbox by requiring some cursor movement (#​3762)

v2.2.5

Compare Source

Fixed
  • Fix listbox closing immediately after opening on touch devices (#​3755)
remix-run/react-router (@​react-router/dev)

v7.14.1

Compare Source

Patch Changes

v7.14.0

Compare Source

Minor Changes
Patch Changes

  • support for prerendering multiple server bundles with v8_viteEnvironmentApi (#​14921)

  • rsc framework mode prerender / spa mode support (#​14907)

  • UNSTABLE RSC FRAMEWORK MODE BREAKING CHANGE - Existing route module exports remain unchanged from stable v7 non-RSC mode, but new exports are added for RSC mode. If you want to use RSC features, you will need to update your route modules to export the new annotations. (#​14901)

    If you are using RSC framework mode currently, you will need to update your route modules to the new conventions. The following route module components have their own mutually exclusive server component counterparts:

    Server Component Export Client Component
    ServerComponent default
    ServerErrorBoundary ErrorBoundary
    ServerLayout Layout
    ServerHydrateFallback HydrateFallback

    If you were previously exporting a ServerComponent, your ErrorBoundary, Layout, and HydrateFallback were also server components. If you want to keep those as server components, you can rename them and prefix them with Server. If you were previously importing the implementations of those components from a client module, you can simply inline them.

    Example:

    Before

    import { ErrorBoundary as ClientErrorBoundary } from "./client";

export function ServerComponent() {
  // ...
}

export function ErrorBoundary() {
  return <ClientErrorBoundary />;
}

export function Layout() {
  // ...
}

export function HydrateFallback() {
  // ...
}

    After

    export function ServerComponent() {
  // ...
}

export function ErrorBoundary() {
  // previous implementation of ClientErrorBoundary, this is now a client component
}

export function ServerLayout() {
  // rename previous Layout export to ServerLayout to make it a server component
}

export function ServerHydrateFallback() {
  // rename previous HydrateFallback export to ServerHydrateFallback to make it a server component
}

  • update the reveal command to support rsc for entry.client, entry.rsc, entry.ssr (#​14904)

  • Updated dependencies:

    • react-router@7.14.0
    • @react-router/node@7.14.0
    • @react-router/serve@7.14.0

v7.13.2

Compare Source

Patch Changes

  • Fix react-router dev crash when Unix socket files exist in the project root (#​14854)

  • Escape redirect locations in prerendered redirect HTML (#​14880)

  • Add future.unstable_passThroughRequests flag (#​14775)

    By default, React Router normalizes the request.url passed to your loader, action, and middleware functions by removing React Router's internal implementation details (.data suffixes, index + _routes query params).

    Enabling this flag removes that normalization and passes the raw HTTP request instance to your handlers. This provides a few benefits:

    • Reduces server-side overhead by eliminating multiple new Request() calls on the critical path
    • Allows you to distinguish document from data requests in your handlers base don the presence of a .data suffix (useful for observability purposes)

    If you were previously relying on the normalization of request.url, you can switch to use the new sibling unstable_url parameter which contains a URL instance representing the normalized location:

    // ❌ Before: you could assume there was no `.data` suffix in `request.url`
export async function loader({ request }: Route.LoaderArgs) {
  let url = new URL(request.url);
  if (url.pathname === "/path") {
    // This check will fail with the flag enabled because the `.data` suffix will
    // exist on data requests
  }
}

// ✅ After: use `unstable_url` for normalized routing logic and `request.url`
// for raw routing logic
export async function loader({ request, unstable_url }: Route.LoaderArgs) {
  if (unstable_url.pathname === "/path") {
    // This will always have the `.data` suffix stripped
  }

  // And now you can distinguish between document versus data requests
  let isDataRequest = new URL(request.url).pathname.endsWith(".data");
}

  • Add a new unstable_url: URL parameter to route handler methods (loader, action, middleware, etc.) representing the normalized URL the application is navigating to or fetching, with React Router implementation details removed (.datasuffix, index/_routes query params) (#​14775)

    This is being added alongside the new future.unstable_passthroughRequests future flag so that users still have a way to access the normalized URL when that flag is enabled and non-normalized request's are being passed to your handlers. When adopting this flag, you will only need to start leveraging this new parameter if you are relying on the normalization of request.url in your application code.

    If you don't have the flag enabled, then unstable_url will match request.url.

  • Updated dependencies:

    • react-router@7.13.2
    • @react-router/node@7.13.2
    • @react-router/serve@7.13.2

v7.13.1

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.13.1
    • @react-router/node@7.13.1
    • @react-router/serve@7.13.1

v7.13.0

Compare Source

Patch Changes

v7.12.0

Compare Source

Minor Changes
  • Add additional layer of CSRF protection by rejecting submissions to UI routes from external origins. If you need to permit access to specific external origins, you can specify them in the react-router.config.ts config allowedActionOrigins field. (#​14708)
Patch Changes

  • Fix Maximum call stack size exceeded errors when HMR is triggered against code with cyclic imports (#​14522)

  • fix(vite): Skip SSR middleware in preview server for SPA mode (#​14673)

  • [UNSTABLE] Add a new future.unstable_trailingSlashAwareDataRequests flag to provide consistent behavior of request.pathname inside middleware, loader, and action functions on document and data requests when a trailing slash is present in the browser URL. (#​14644)

    Currently, your HTTP and request pathnames would be as follows for /a/b/c and /a/b/c/

    URL /a/b/c HTTP pathname request pathname`
    Document /a/b/c /a/b/c ✅
    Data /a/b/c.data /a/b/c ✅
    URL /a/b/c/ HTTP pathname request pathname`
    Document /a/b/c/ /a/b/c/ ✅
    Data /a/b/c.data /a/b/c ⚠️

    With this flag enabled, these pathnames will be made consistent though a new _.data format for client-side .data requests:

    URL /a/b/c HTTP pathname request pathname`
    Document /a/b/c /a/b/c ✅
    Data /a/b/c.data /a/b/c ✅
    URL /a/b/c/ HTTP pathname request pathname`
    Document /a/b/c/ /a/b/c/ ✅
    Data /a/b/c/_.data ⬅️ /a/b/c/ ✅

    This a bug fix but we are putting it behind an opt-in flag because it has the potential to be a "breaking bug fix" if you are relying on the URL format for any other application or caching logic.

    Enabling this flag also changes the format of client side .data requests from /_root.data to /_.data when navigating to / to align with the new format. This does not impact the request pathname which is still / in all cases.

  • Updated dependencies:

    • react-router@7.12.0
    • @react-router/node@7.12.0
    • @react-router/serve@7.12.0

v7.11.0

Compare Source

Minor Changes
Patch Changes
  • rsc framework mode manual chunking for react and react-router deps (#​14655)
  • add support for throwing redirect Response's at RSC render time (#​14596)
  • support custom entrypoints for RSC framework mode (#​14643)
  • routeRSCServerRequest replace fetchServer with serverResponse (#​14597)
  • rsc framewlrk mode - optimize react-server-dom-webpack if in project package.json (#​14656)
  • Updated dependencies:
    • react-router@7.11.0
    • @react-router/serve@7.11.0
    • @react-router/node@7.11.0

v7.10.1

Compare Source

Patch Changes
  • Import ESM package pkg-types with a dynamic import() to fix issues on Node 20.18 (#​14624)
  • Update valibot dependency to ^1.2.0 to address GHSA-vqpr-j7v3-hqw9 (#​14608)
  • Updated dependencies:
    • react-router@7.10.1
    • @react-router/node@7.10.1
    • @react-router/serve@7.10.1

v7.10.0

Compare Source

Minor Changes

  • Stabilize future.v8_splitRouteModules, replacing future.unstable_splitRouteModules (#​14595)

    • ⚠️ This is a breaking change if you have begun using future.unstable_splitRouteModules. Please update your react-router.config.ts.

  • Stabilize future.v8_viteEnvironmentApi, replacing future.unstable_viteEnvironmentApi (#​14595)

    • ⚠️ This is a breaking change if you have begun using future.unstable_viteEnvironmentApi. Please update your react-router.config.ts.
Patch Changes

  • Load environment variables before evaluating routes.ts (#​14446)

    For example, you can now compute your routes based on VITE_-prefixed environment variables:

    # .env
VITE_ENV_ROUTE=my-route
    // app/routes.ts
import { type RouteConfig, route } from "@&#8203;react-router/dev/routes";

const routes: RouteConfig = [];
if (import.meta.env.VITE_ENV_ROUTE === "my-route") {
  routes.push(route("my-route", "routes/my-route.tsx"));
}

export default routes;

  • Updated dependencies:

    • react-router@7.10.0
    • @react-router/node@7.10.0
    • @react-router/serve@7.10.0

v7.9.6

Compare Source

Patch Changes
  • Use a dynamic import() to load ESM-only p-map dependency to avoid issues on Node 20.18 and below (#​14492)
  • Short circuit HEAD document requests before calling renderToPipeableStream in the default entry.server.tsx to more closely align with the spec (#​14488)
  • Updated dependencies:
    • react-router@7.9.6
    • @react-router/node@7.9.6
    • @react-router/serve@7.9.6

v7.9.5

Compare Source

Patch Changes
  • Introduce a prerender.unstable_concurrency option, to support running the prerendering concurrently, potentially speeding up the build. (#​14380)
  • Move RSCHydratedRouter and utils to /dom export. (#​14457)
  • Ensure route navigation doesn't remove CSS link elements used by dynamic imports (#​14463)
  • Typegen: only register route module types for routes within the app directory (#​14439)
  • Updated dependencies:
    • react-router@7.9.5
    • @react-router/node@7.9.5
    • @react-router/serve@7.9.5

v7.9.4

Compare Source

Patch Changes

  • Update valibot dependency to ^1.1.0 (#​14379)

  • New (unstable) useRoute hook for accessing data from specific routes (#​14407)

    For example, let's say you have an admin route somewhere in your app and you want any child routes of admin to all have access to the loaderData and actionData from admin.

    // app/routes/admin.tsx
import { Outlet } from "react-router";

export const loader = () => ({ message: "Hello, loader!" });

export const action = () => ({ count: 1 });

export default function Component() {
  return (
    <div>
      {/* ... */}
      <Outlet />
      {/* ... */}
    </div>
  );
}

    You might even want to create a reusable widget that all of the routes nested under admin could use:

    import { unstable_useRoute as useRoute } from "react-router";

export function AdminWidget() {
  // How to get `message` and `count` from `admin` route?
}

    In framework mode, useRoute knows all your app's routes and gives you TS errors when invalid route IDs are passed in:

    export function AdminWidget() {
  const admin = useRoute("routes/dmin");
  //                      ^^^^^^^^^^^
}

    useRoute returns undefined if the route is not part of the current page:

    export function AdminWidget() {
  const admin = useRoute("routes/admin");
  if (!admin) {
    throw new Error(`AdminWidget used outside of "routes/admin"`);
  }
}

    Note: the root route is the exception since it is guaranteed to be part of the current page.
    As a result, useRoute never returns undefined for root.

    loaderData and actionData are marked as optional since they could be accessed before the action is triggered or after the loader threw an error:

    export function AdminWidget() {
  const admin = useRoute("routes/admin");
  if (!admin) {
    throw new Error(`AdminWidget used outside of "routes/admin"`);
  }
  const { loaderData, actionData } = admin;
  console.log(loaderData);
  //          ^? { message: string } | undefined
  console.log(actionData);
  //          ^? { count: number } | undefined
}

    If instead of a specific route, you wanted access to the current route's loaderData and actionData, you can call useRoute without arguments:

    export function AdminWidget() {
  const currentRoute = useRoute();
  currentRoute.loaderData;
  currentRoute.actionData;
}

    This usage is equivalent to calling useLoaderData and useActionData, but consolidates all route data access into one hook: useRoute.

    Note: when calling useRoute() (without a route ID), TS has no way to know which route is the current route.
    As a result, loaderData and actionData are typed as unknown.
    If you want more type-safety, you can either narrow the type yourself with something like zod or you can refactor your app to pass down typed props to your AdminWidget:

    export function AdminWidget({
  message,
  count,
}: {
  message: string;
  count: number;
}) {
  /* ... */
}

  • Updated dependencies:

    • react-router@7.9.4
    • @react-router/node@7.9.4
    • @react-router/serve@7.9.4

v7.9.3

Compare Source

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

v7.9.2

Compare Source

Patch Changes

  • Fix preset future flags being ignored during config resolution (#​14369)

    Fixes a bug where future flags defined by presets were completely ignored. The config resolution was incorrectly reading from reactRouterUserConfig.future instead of the merged userAndPresetConfigs.future, causing all preset-defined future flags to be lost.

    This fix ensures presets can properly enable experimental features as intended by the preset system design.

  • Add unstable support for RSC Framework Mode (#​14336)

  • Switch internal vite plugin Response logic to use @remix-run/node-fetch-server (#​13927)

  • Updated dependencies:

    • react-router@7.9.2
    • @react-router/serve@7.9.2
    • @react-router/node@7.9.2

v7.9.1

Compare Source

Patch Changes
  • Fix internal Future interface naming from middleware -> v8_middleware (#​14327)
  • Updated dependencies:
    • react-router@7.9.1
    • @react-router/node@7.9.1
    • @react-router/serve@7.9.1

v7.9.0

Compare Source

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

v7.8.2

Compare Source

Patch Changes
  • fix: memory leak in default entry.server (#​14200)
  • Updated dependencies:
    • react-router@7.8.2
    • @react-router/node@7.8.2
    • @react-router/serve@7.8.2

v7.8.1

Compare Source

Patch Changes
  • Update generated Route.MetaArgs type so loaderData is only potentially undefined when an ErrorBoundary export is present (#​14173)
  • Updated dependencies:
    • react-router@7.8.1
    • @react-router/node@7.8.1
    • @react-router/serve@7.8.1

v7.8.0

Compare Source

Patch Changes
  • Fix rename without mkdir in Vite plugin (#​14105)
  • Updated dependencies:
    • react-router@7.8.0
    • @react-router/node@7.8.0
    • @react-router/serve@7.8.0

v7.7.1

Compare Source

Patch Changes
  • Update to Prettier v3 for formatting when running react-router reveal --no-typescript (#​14049)
  • Updated dependencies:
    • react-router@7.7.1
    • @react-router/node@7.7.1
    • @react-router/serve@7.7.1

v7.7.0

Compare Source

Patch Changes
  • Update vite-node to ^3.2.2 to support Vite 7 (#​13781)
  • Properly handle https protocol in dev mode (#​13746)
  • Fix missing styles when Vite's build.cssCodeSplit option is disabled (#​13943)
  • Allow .mts and .mjs extensions for route config file (#​13931)
  • Fix prerender file locations when cwd differs from project root (#​13824)
  • Improve chunk error logging when a chunk cannot be found during the build (#​13799)
  • Fix incorrectly configured externalConditions which had enabled module condition for externals and broke builds with certain packages, like Emotion. (#​13871)
  • Updated dependencies:
    • react-router@7.7.0
    • @react-router/node@7.7.0
    • @react-router/serve@7.7.0

v7.6.3

Compare Source

Patch Changes
  • Add Vite 7 support (#​13748)
  • Skip package.json resolution checks when a custom entry.server.(j|t)sx file is provided. (#​13744)
  • Add validation for a route's id not being 'root' (#​13792)
  • Updated dependencies:
    • @react-router/node@7.6.3
    • react-router@7.6.3
    • @react-router/serve@7.6.3
remix-run/react-router (@​react-router/serve)

v7.14.1

Compare Source

Patch Changes

v7.14.0

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.14.0
    • @react-router/node@7.14.0
    • @react-router/express@7.14.0

v7.13.2

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.13.2
    • @react-router/node@7.13.2
    • @react-router/express@7.13.2

v7.13.1

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.13.1
    • @react-router/node@7.13.1
    • @react-router/express@7.13.1

v7.13.0

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.13.0
    • @react-router/node@7.13.0
    • @react-router/express@7.13.0

v7.12.0

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.12.0
    • @react-router/node@7.12.0
    • @react-router/express@7.12.0

v7.11.0

Compare Source

Patch Changes
  • support custom entrypoints for RSC framework mode (#​14643)
  • Update compression and morgan dependencies to address on-headers CVE: GHSA-76c9-3jph-rj3q (#​14652)
  • Updated dependencies:
    • react-router@7.11.0
    • @react-router/node@7.11.0
    • @react-router/express@7.11.0

v7.10.1

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.10.1
    • @react-router/node@7.10.1
    • @react-router/express@7.10.1

v7.10.0

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.10.0
    • @react-router/node@7.10.0
    • @react-router/express@7.10.0

v7.9.6

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.9.6
    • @react-router/node@7.9.6
    • @react-router/express@7.9.6

v7.9.5

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.9.5
    • @react-router/node@7.9.5
    • @react-router/express@7.9.5

v7.9.4

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.9.4
    • @react-router/node@7.9.4
    • @react-router/express@7.9.4

v7.9.3

Compare Source

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

v7.9.2

Compare Source

Patch Changes
  • disable compression for RSC responses for now (#​14381)
  • Updated dependencies:
    • react-router@7.9.2
    • @react-router/node@7.9.2
    • @react-router/express@7.9.2

v7.9.1

Compare Source

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

v7.9.0

Compare Source

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

v7.8.2

Compare Source

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

v7.8.1

Compare Source

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

v7.8.0

Compare Source

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

v7.7.1

[Compare Source](https://redirect.github.com/remix-run/react-router/compare/@react-router/serve@7.7.0...@react-route

Configuration

📅 Schedule: (in timezone Europe/Berlin)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

@forking-renovate
Copy link
Copy Markdown

forking-renovate bot commented Mar 9, 2026 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @undefined
npm error Found: react-router@7.6.2
npm error node_modules/react-router
npm error   react-router@"^7.5.3" from the root project
npm error   peer react-router@"7.6.2" from @react-router/express@7.6.2
npm error   node_modules/@react-router/express
npm error   1 more (@react-router/node)
npm error
npm error Could not resolve dependency:
npm error dev @react-router/dev@"7.14.1" from the root project
npm error
npm error Conflicting peer dependency: react-router@7.14.1
npm error node_modules/react-router
npm error   peer react-router@"^7.14.1" from @react-router/dev@7.14.1
npm error   node_modules/@react-router/dev
npm error     dev @react-router/dev@"7.14.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-15T11_14_42_828Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-15T11_14_42_828Z-debug-0.log

@netlify
Copy link
Copy Markdown

netlify bot commented Mar 9, 2026 •
edited
Loading

❌ Deploy Preview for verify-sourcify-ui failed. Why did it fail? →

Name Link
🔨 Latest commit 514acf6
🔍 Latest deploy log https://app.netlify.com/projects/verify-sourcify-ui/deploys/69df732dae2ed60008bda1f8

@renovate-bot renovate-bot force-pushed the renovate/all-patch-and-minor branch 2 times, most recently from cf668e8 to a940c85 Compare March 17, 2026 13:19
@renovate-bot renovate-bot force-pushed the renovate/all-patch-and-minor branch 3 times, most recently from 2bc7adf to 32cc993 Compare March 23, 2026 16:58
@renovate-bot renovate-bot changed the title Update all patch and minor dependencies fix(deps): update all patch and minor dependencies Mar 26, 2026
@renovate-bot renovate-bot force-pushed the renovate/all-patch-and-minor branch 4 times, most recently from 07b8afe to 470fef8 Compare March 31, 2026 01:44
@manuelwedler
Copy link
Copy Markdown
Member

manuelwedler commented Apr 1, 2026

@claude please fix this PR.

@manuelwedler manuelwedler moved this to Sprint - Needs Review in Sourcify Public Apr 1, 2026
@renovate-bot renovate-bot force-pushed the renovate/all-patch-and-minor branch 8 times, most recently from 79bead8 to 38d0266 Compare April 8, 2026 21:05
@renovate-bot renovate-bot changed the title fix(deps): update all patch and minor dependencies Update all patch and minor dependencies Apr 8, 2026
@renovate-bot renovate-bot force-pushed the renovate/all-patch-and-minor branch 3 times, most recently from 88e52bd to 13e4acf Compare April 13, 2026 22:32
@renovate-bot renovate-bot force-pushed the renovate/all-patch-and-minor branch from 13e4acf to 514acf6 Compare April 15, 2026 11:14
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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@renovate-bot @manuelwedler