fix(deps): Update npm dependencies [backport]

[jharvey10]

Backport of the following:

This PR contains the following updates:

Package	Change	Age	Confidence	Type	Update
@dagrejs/dagre	^1.1.5 → ^1.1.8			dependencies	patch
@eslint/js (source)	^9.34.0 → 9.38.0			devDependencies	pin
@grafana/data (source)	^11.6.5 → ^11.6.9			dependencies	patch
@grafana/ui (source)	^11.6.7 → ^11.6.9			dependencies	patch
@types/d3 (source)	^7.4.3 → 7.4.3			devDependencies	pin
@types/d3-zoom (source)	^3.0.8 → 3.0.8			devDependencies	pin
@types/react (source)	^18.3.26 → 18.3.26			devDependencies	pin
@types/react-dom (source)	^18.3.7 → 18.3.7			devDependencies	pin
@vitejs/plugin-react (source)	^5.1.0 → 5.1.0			devDependencies	pin
@xyflow/react (source)	^12.9.2 → ^12.10.0			dependencies	minor
eslint (source)	^9.38.0 → 9.38.0			devDependencies	pin
eslint-plugin-react-hooks (source)	^5.2.0 → 5.2.0			devDependencies	pin
eslint-plugin-react-refresh	^0.4.24 → 0.4.24			devDependencies	pin
eslint-plugin-simple-import-sort	^12.1.1 → 12.1.1			devDependencies	pin
globals	^16.4.0 → 16.4.0			devDependencies	pin
prettier (source)	^3.6.2 → 3.6.2			devDependencies	pin
react-router (source)	^7.9.5 → ^7.11.0			dependencies	minor
typescript (source)	^5.9.3 → 5.9.3			devDependencies	pin
typescript-eslint (source)	^8.46.2 → 8.46.2			devDependencies	pin
vite (source)	^7.1.12 → 7.1.12			devDependencies	pin

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

dagrejs/dagre (@​dagrejs/dagre)

v1.1.8

Compare Source

grafana/grafana (@​grafana/data)

v11.6.9: 11.6.9

Compare Source

Download page
What's new highlights

Features and enhancements

• Alerting: Update alerting dependency #​114249, @​moustafab
• Dependencies: Bump Go to v1.25.5 #​114757, @​macabu
• PDFTables: Dynamically shrink font to try and fit whole table in pdf page width (Enterprise)
• Plugins: Add PluginContext to plugins when scenes is disabled #​115060, @​hugohaggmark

Bug fixes

• Alerting: Fix contacts point issues #​115409, @​yuri-tceretian

v11.6.8: 11.6.8

Compare Source

Download page
What's new highlights

Bug fixes

• Alerting: Fix unmarshalling of GettableStatus to include time intervals #​112731, @​yuri-tceretian
• AnalyticsSummaries: Fix dashboard rollup not resetting "last X days" metrics to zero (Enterprise)
• AnalyticsSummaries: Fix dashboard rollup totals resetting incorrectly (Enterprise)
• Seeder: Add check in filterRemovedPermissions for already existing new permissions before seeding (Enterprise)

xyflow/xyflow (@​xyflow/react)

v12.10.0

Compare Source

Minor Changes

• #​5637 0c7261a6d Thanks @​moklick! - Add zIndexMode to control how z-index is calculated for nodes and edges

• #​5484 a523919d6 Thanks @​peterkogo! - Add experimental_useOnNodesChangeMiddleware hook

Patch Changes

• #​5629 9030fab2d Thanks @​AlaricBaraou! - Prevent unnecessary re-render in FlowRenderer

• #​5592 38dbf41c4 Thanks @​svilen-ivanov-kubit! - Always create a new measured object in apply changes.

• #​5635 2d7fa40e2 Thanks @​tornado-softwares! - Update an ongoing connection when user moves node with keyboard.

• Updated dependencies [0c7261a6d, 8598b6bc2, 2d7fa40e2]:

  • @​xyflow/system@​0.0.74

v12.9.3

Compare Source

Patch Changes

• #​5621 c1304dba7 Thanks @​moklick! - Set paneClickDistance default value to 1.

• #​5578 00bcb9f5f Thanks @​peterkogo! - Pass current pointer position to connection

• Updated dependencies [00bcb9f5f]:

  • @​xyflow/system@​0.0.73

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

v7.11.0

Compare Source

Minor Changes

• Stabilize <HydratedRouter onError>/<RouterProvider onError> (#​14546)

Patch Changes

• add support for throwing redirect Response's at RSC render time (#​14596)

• Support for throwing data() and Response from server component render phase. Response body is not serialized as async work is not allowed as error encoding phase. If you wish to transmit data to the boundary, throw data() instead. (#​14632)

• Fix unstable_useTransitions prop on <Router> component to permit omission for backewards compatibility (#​14646)

• routeRSCServerRequest replace fetchServer with serverResponse (#​14597)

• [UNSTABLE] Add a new unstable_defaultShouldRevalidate flag to various APIs to allow opt-ing out of standard revalidation behaviors. (#​14542)

  If active routes include a shouldRevalidate function, then your value will be passed as defaultShouldRevalidate in those function so that the route always has the final revalidation determination.

  • <Form method="post" unstable_defaultShouldRevalidate={false}>
  • submit(data, { method: "post", unstable_defaultShouldRevalidate: false })
  • <fetcher.Form method="post" unstable_defaultShouldRevalidate={false}>
  • fetcher.submit(data, { method: "post", unstable_defaultShouldRevalidate: false })

  This is also available on non-submission APIs that may trigger revalidations due to changing search params:

  • <Link to="/" unstable_defaultShouldRevalidate={false}>
  • navigate("/?foo=bar", { unstable_defaultShouldRevalidate: false })
  • setSearchParams(params, { unstable_defaultShouldRevalidate: false })

• Allow redirects to be returned from client side middleware (#​14598)

• Handle dataStrategy implementations that return insufficient result sets by adding errors for routes without any available result (#​14627)

v7.10.1

Compare Source

Patch Changes

• Update the useOptimistic stub we provide for React 18 users to use a stable setter function to avoid potential useEffect loops - specifically when using <Link viewTransition> (#​14628)

v7.10.0

Compare Source

Minor Changes

• Stabilize fetcher.reset() (#​14545)

  • ⚠️ This is a breaking change if you have begun using fetcher.unstable_reset()

• Stabilize the dataStrategy match.shouldRevalidateArgs/match.shouldCallHandler() APIs. (#​14592)

  • The match.shouldLoad API is now marked deprecated in favor of these more powerful alternatives

  • If you're using this API in a custom dataStrategy today, you can swap to the new API at your convenience:

    // Before
    const matchesToLoad = matches.filter((m) => m.shouldLoad);
    
    // After
    const matchesToLoad = matches.filter((m) => m.shouldCallHandler());

  • match.shouldRevalidateArgs is the argument that will be passed to the route shouldRevaliate function

  • Combined with the parameter accepted by match.shouldCallHandler, you can define a custom revalidation behavior for your dataStrategy:

  const matchesToLoad = matches.filter((m) => {
    const defaultShouldRevalidate = customRevalidationBehavior(
      match.shouldRevalidateArgs,
    );
    return m.shouldCallHandler(defaultShouldRevalidate);
    // The argument here will override the internal `defaultShouldRevalidate` value
  });

Patch Changes

• Fix a Framework Mode bug where the defaultShouldRevalidate parameter to shouldRevalidate would not be correct after action returned a 4xx/5xx response (true when it should have been false) (#​14592)

  • If your shouldRevalidate function relied on that parameter, you may have seen unintended revalidations

• Fix fetcher.submit failing with plain objects containing a tagName property (#​14534)

• [UNSTABLE] Add unstable_pattern to the parameters for client side unstable_onError, refactor how it's called by RouterProvider to avoid potential strict mode issues (#​14573)

• Add new unstable_useTransitions flag to routers to give users control over the usage of React.startTransition and React.useOptimistic. (#​14524)

  • Framework Mode + Data Mode:
    • <HydratedRouter unstable_transition>/<RouterProvider unstable_transition>
    • When left unset (current default behavior)
      • Router state updates are wrapped in React.startTransition
      • ⚠️ This can lead to buggy behaviors if you are wrapping your own navigations/fetchers in React.startTransition
      • You should set the flag to true if you run into this scenario to get the enhanced useOptimistic behavior (requires React 19)
    • When set to true
      • Router state updates remain wrapped in React.startTransition (as they are without the flag)
      • Link/Form navigations will be wrapped in React.startTransition
      • A subset of router state info will be surfaced to the UI during navigations via React.useOptimistic (i.e., useNavigation(), useFetchers(), etc.)
        • ⚠️ This is a React 19 API so you must also be React 19 to opt into this flag for Framework/Data Mode
    • When set to false
      • The router will not leverage React.startTransition or React.useOptimistic on any navigations or state changes
  • Declarative Mode
    • <BrowserRouter unstable_useTransitions>
    • When left unset
      • Router state updates are wrapped in React.startTransition
    • When set to true
      • Router state updates remain wrapped in React.startTransition (as they are without the flag)
      • Link/Form navigations will be wrapped in React.startTransition
    • When set to false
      • the router will not leverage React.startTransition on any navigations or state changes

• Fix the promise returned from useNavigate in Framework/Data Mode so that it properly tracks the duration of popstate navigations (i.e., navigate(-1)) (#​14524)

• Fix internal type error in useRoute types that surfaces when skipLibCheck is disabled (#​14577)

• Preserve statusText on the ErrorResponse instance when throwing data() from a route handler (#​14555)

• Optimize href() to avoid backtracking regex on splat (#​14329)

v7.9.6

Compare Source

Patch Changes

• [UNSTABLE] Add location/params as arguments to client-side unstable_onError to permit enhanced error reporting. (#​14509)

  ⚠️ This is a breaking change if you've already adopted unstable_onError. The second errorInfo parameter is now an object with location and params:

  // Before
  function errorHandler(error: unknown, errorInfo?: React.errorInfo) {
    /*...*/
  }
  
  // After
  function errorHandler(
    error: unknown,
    info: {
      location: Location;
      params: Params;
      errorInfo?: React.ErrorInfo;
    },
  ) {
    /*...*/
  }

• Properly handle ancestor thrown middleware errors before next() on fetcher submissions (#​14517)

• Fix issue with splat routes interfering with multiple calls to patchRoutesOnNavigation (#​14487)

• Normalize double-slashes in resolvePath (#​14529)

---

Configuration

📅 Schedule: Branch creation - Between 06:00 AM and 10:59 AM, only on Monday ( * 6-10 * * 1 ) (UTC), 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

---

Need help?

You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.