• test: remove stale deploy manifest exclusions: #98051
• Enable hourly next-maintainer auto-close workflow: #98225
• Return client errors for unrecognized Server Actions: #98123
• Add Next Maintainer auto-close workflow: #98197
• perf(turbopack): skip ignored files during server tracing: #97475
• docs: note that experimental.taint taints process.env: #98145
• test: preserve static params during Cache Components migration: #98209
• Upgrade web-vitals to v6 and report soft navigations: #97232
• Upgrade React from 21c89c9f-20260901 to f4e439e1-20260902: #98188

Huge thanks to @gnoff, @marcoshernanz, @jimmyhmiller, @icyJoseph, @aurorascharff, and @timneutkens for helping!

Release 2026-09-03 20:13

• solid-router: native SSR match transfer, hydration-claiming boot, provider-owned dispatch (#8213) (b445b89281) by @ryansolid
• solid: named single-flight source + loadFlightTarget, the cache-agnostic trigger (#8192) (96f50d94a6) by @ryansolid

• examples: migrate remaining legacy createEffect calls to Solid 2.0 two-phase signature (#8223) (c753d0a222) by @ryansolid

• solid: retire solid-router-ssr-query — native channels carry the Router + Query pairing (#8193) (5a6935f2d5) by @ryansolid

• @tanstack/solid-router@2.0.0-rc.5
• @tanstack/solid-router-devtools@2.0.0-rc.5
• @tanstack/solid-router-ssr-query@2.0.0-rc.5
• @tanstack/solid-start@2.0.0-rc.5
• @tanstack/solid-start-client@2.0.0-rc.5
• @tanstack/solid-start-server@2.0.0-rc.5

• #8192 96f50d9 - Bump solid-js, @solidjs/web, and @solidjs/signals to ^2.0.0-rc.6 across the monorepo. rc.6 provides the named flight-data source API (registerFlightDataSource / two-argument subscribeFlightData) that the Start single-flight integration now requires; @tanstack/solid-start's peer floor moves to rc.6 accordingly.

• #8192 96f50d9 - Adopt Solid's multi-source single-flight protocol: the router's flight data (loader/match state, dehydrated data) registers under its own source id (tsr), so other caches' slices — e.g. solid-query's sq — coexist on the same mutation response instead of competing for a single consumer slot, and a user-supplied collectFlightData hook adds data alongside the router's rather than displacing it. Requires solid-js / @solidjs/web 2.0.0-rc.6+ (named flight-data sources).

• Updated dependencies [96f50d9, 96f50d9, b445b89]:

  • @tanstack/solid-router@2.0.0-rc.5
  • @tanstack/solid-start-client@2.0.0-rc.5
  • @tanstack/solid-start-server@2.0.0-rc.5

• #8192 96f50d9 - Bump solid-js, @solidjs/web, and @solidjs/signals to ^2.0.0-rc.6 across the monorepo. rc.6 provides the named flight-data source API (registerFlightDataSource / two-argument subscribeFlightData) that the Start single-flight integration now requires; @tanstack/solid-start's peer floor moves to rc.6 accordingly.

• Updated dependencies [96f50d9, 96f50d9, b445b89]:

  • @tanstack/solid-router@2.0.0-rc.5

• #8192 96f50d9 - Bump solid-js, @solidjs/web, and @solidjs/signals to ^2.0.0-rc.6 across the monorepo. rc.6 provides the named flight-data source API (registerFlightDataSource / two-argument subscribeFlightData) that the Start single-flight integration now requires; @tanstack/solid-start's peer floor moves to rc.6 accordingly.

• #8193 5a6935f - Deprecated: Solid Query's QueryClientProvider now carries the Router + Query SSR pairing natively (registry hydration, named single-flight sources, redirect handling via userland glue), so this integration package is no longer needed. See the README for the migration.

• #8192 96f50d9 - Bump solid-js, @solidjs/web, and @solidjs/signals to ^2.0.0-rc.6 across the monorepo. rc.6 provides the named flight-data source API (registerFlightDataSource / two-argument subscribeFlightData) that the Start single-flight integration now requires; @tanstack/solid-start's peer floor moves to rc.6 accordingly.

• #8192 96f50d9 - New loadFlightTarget helper (exported from @tanstack/solid-router/ssr/server): the router's half of a single-flight refresh. Given the mutation request's target href, it builds a router for that location, loads it, and returns the dehydrated payload for the tsr flight-data slice, so server collectors can refresh router state alongside other caches on the same mutation response.

• #8213 b445b89 - Native SSR state transfer for Solid: router match state (loaderData, beforeLoad context, status, errors) now rides Solid's hydration registry under tsr: keys instead of a bespoke bootstrap script, deferred loaderData promises stream natively via seroval, the client primes router state from the registry in the Router constructor (before any render context, eliminating boot-time refetches and bootLoad-style workarounds), and RouterProvider owns the server-side router.load() dispatch so server entries no longer await it manually.

• #8192 96f50d9 - Bump solid-js, @solidjs/web, and @solidjs/signals to ^2.0.0-rc.6 across the monorepo. rc.6 provides the named flight-data source API (registerFlightDataSource / two-argument subscribeFlightData) that the Start single-flight integration now requires; @tanstack/solid-start's peer floor moves to rc.6 accordingly.

• Updated dependencies [96f50d9, 96f50d9, b445b89]:

  • @tanstack/solid-router@2.0.0-rc.5

• #8192 96f50d9 - Bump solid-js, @solidjs/web, and @solidjs/signals to ^2.0.0-rc.6 across the monorepo. rc.6 provides the named flight-data source API (registerFlightDataSource / two-argument subscribeFlightData) that the Start single-flight integration now requires; @tanstack/solid-start's peer floor moves to rc.6 accordingly.

• Updated dependencies [96f50d9, 96f50d9, b445b89]:

  • @tanstack/solid-router@2.0.0-rc.5

Note: This is an alpha release. Please file new issues for any bugs you find in it.

This release is published to npm under the alpha tag and can be installed via npm install electron@alpha, or npm install electron@45.0.0-alpha.4.

• Fixed chrome.tabs.query() returning tab url and title to extensions without the tabs permission or host access, aligning with tabs.get. #53353 ^{(Also in 42, 43, 44)}
• Fixed a pending read on a net.request chunked upload stream inside a protocol handler never settling when the request failed or was aborted. #53368 ^{(Also in 43, 44)}
• Fixed an intermittent crash (access violation) on Windows when an ASAR integrity violation is detected, so the process now exits with code 1 as intended. #53438 ^{(Also in 43, 44)}
• Fixed application crash after a large number of IPC messages from renderers. #53418 ^{(Also in 42, 43, 44)}
• Fixed native addons deriving from node::ObjectWrap aborting during garbage collection on Node.js 24.19.0 and later. #53391 ^{(Also in 42, 43, 44)}

• Updated Chromium to 155.0.8038.2. #53416
• Updated Node.js to v24.20.0. #53251

• build(deps): align Renovate Bazel lock command by @longlho in https://github.com/formatjs/formatjs/pull/7122
• build: cross-compile Python release wheels by @longlho in https://github.com/formatjs/formatjs/pull/7121
• fix: rename Python intl distribution by @longlho in https://github.com/formatjs/formatjs/pull/7123
• fix: validate released Python versions by @longlho in https://github.com/formatjs/formatjs/pull/7125
• feat(formatjs_cli): extract Python format_message calls by @longlho in https://github.com/formatjs/formatjs/pull/7129
• feat(formatjs_intl): align Python runtime fallback by @longlho in https://github.com/formatjs/formatjs/pull/7130
• chore: release main by @formatjsproject in https://github.com/formatjs/formatjs/pull/7133
• build(deps): update Bazel lockfiles for Renovate PRs by @longlho in https://github.com/formatjs/formatjs/pull/7135
• build(deps): publish dispatched Renovate check results by @longlho in https://github.com/formatjs/formatjs/pull/7136
• build(deps): publish Renovate required statuses by @longlho in https://github.com/formatjs/formatjs/pull/7137
• fix(eslint-plugin-formatjs): align message recognition across tools by @longlho in https://github.com/formatjs/formatjs/pull/7151
• fix(babel-plugin-formatjs): support transparent expression wrappers by @longlho in https://github.com/formatjs/formatjs/pull/7156

Full Changelog: https://github.com/formatjs/formatjs/compare/@formatjs/unplugin@1.2.7...@formatjs/unplugin@1.2.8