Bump the core-ui-package-updates group across 1 directory with 16 updates

[dependabot]

Bumps the core-ui-package-updates group with 16 updates in the /airflow-core/src/airflow/ui directory:

Package	From	To
@tanstack/react-query	5.104.0	5.104.2
@tanstack/react-virtual	3.14.13	3.14.17
i18next	26.4.2	26.4.4
react-hook-form	7.89.0	7.90.0
react-i18next	17.0.15	17.0.16
react-resizable-panels	4.14.1	4.14.4
react-syntax-highlighter	16.1.1	16.1.2
@playwright/test	1.63.0	1.64.0
@tanstack/eslint-plugin-query	5.104.0	5.104.2
@types/node	26.6.3	26.6.5
@vitejs/plugin-react	6.1.1	6.1.2
@vitest/coverage-v8	5.0.3	5.0.4
msw	3.0.2	3.0.3
prettier	3.9.9	3.9.10
vite	8.3.3	8.3.4
vitest	5.0.3	5.0.4

Updates @tanstack/react-query from 5.104.0 to 5.104.2

Release notes

Sourced from @​tanstack/react-query's releases.

@​tanstack/react-query-devtools@​5.104.2

Patch Changes

• Updated dependencies []:
  • @​tanstack/query-devtools@​5.104.2
  • @​tanstack/react-query@​5.104.2

@​tanstack/react-query-next-experimental@​5.104.2

Patch Changes

• Updated dependencies []:
  • @​tanstack/react-query@​5.104.2

@​tanstack/react-query-persist-client@​5.104.2

Patch Changes

• Updated dependencies []:
  • @​tanstack/query-persist-client-core@​5.104.2
  • @​tanstack/react-query@​5.104.2

@​tanstack/react-query@​5.104.2

Patch Changes

• Updated dependencies [03e8c39]:
  • @​tanstack/query-core@​5.104.2

@​tanstack/react-query-devtools@​5.104.1

Patch Changes

• Updated dependencies [ec060b6]:
  • @​tanstack/query-devtools@​5.104.1
  • @​tanstack/react-query@​5.104.1

@​tanstack/react-query-next-experimental@​5.104.1

Patch Changes

• Updated dependencies []:
  • @​tanstack/react-query@​5.104.1

@​tanstack/react-query-persist-client@​5.104.1

Patch Changes

• Updated dependencies []:
  • @​tanstack/query-persist-client-core@​5.104.1
  • @​tanstack/react-query@​5.104.1

@​tanstack/react-query@​5.104.1

Patch Changes

• Updated dependencies []:

... (truncated)

Changelog

Sourced from @​tanstack/react-query's changelog.

5.104.2

Patch Changes

• Updated dependencies [03e8c39]:
  • @​tanstack/query-core@​5.104.2

5.104.1

Patch Changes

• Updated dependencies []:
  • @​tanstack/query-core@​5.104.1

Commits

• b699b52 ci: Version Packages (#11849)
• e22e7c4 chore: test TypeScript 7.1 preview and drop 5.6 (#11947)
• df78a9d chore(*): pass the root 'settings' to the package oxlint configs, which 'exte...
• 833062c chore: replace prettier with oxfmt (#11939)
• d0cfa6a chore: replace eslint with oxlint (#11938)
• 0012ec1 docs(react-query): add JSDoc to the properties of the exported interfaces and...
• b5e8e7b docs(react-query): add JSDoc to the exported classes, methods, and arrow func...
• 01abab3 docs(*): note that 'throwOnError' makes the hook rethrow the errors of 'mutat...
• b42166e docs(react-query): add JSDoc to the exported interfaces and type aliases (#11...
• 205d422 docs(*): add missing JSDoc descriptions and enforce 'jsdoc/require-descriptio...
• Additional commits viewable in compare view

Updates @tanstack/react-virtual from 3.14.13 to 3.14.17

Release notes

Sourced from @​tanstack/react-virtual's releases.

@​tanstack/react-virtual@​3.14.17

Patch Changes

• Updated dependencies [3800fb3, cb510cb]:
  • @​tanstack/virtual-core@​3.19.2

@​tanstack/react-virtual@​3.14.16

Patch Changes

• Updated dependencies [7aa34f6, e7a0a92]:
  • @​tanstack/virtual-core@​3.19.1

@​tanstack/react-virtual@​3.14.15

Patch Changes

• Updated dependencies [28a2174, 92c697f]:
  • @​tanstack/virtual-core@​3.19.0

@​tanstack/react-virtual@​3.14.14

Patch Changes

• #1301 ce57b78 - fix(react-virtual): position directDomUpdates rows that mount without the owner re-rendering

  Rows were only positioned by the owner's layout effect or the next onChange. A row mounted by a child that re-renders on its own (local state, context, a resolved Suspense boundary) skipped both when it was fixed-size, and stayed unpositioned until the range changed. Rows are now positioned as they register through measureElement, and containerRef positions the rows that mounted together with the container.

• Updated dependencies [43675bc, 9df47a3, c644f10, 2a631f4]:

  • @​tanstack/virtual-core@​3.18.0

Changelog

Sourced from @​tanstack/react-virtual's changelog.

3.14.17

Patch Changes

• Updated dependencies [3800fb3, cb510cb]:
  • @​tanstack/virtual-core@​3.19.2

3.14.16

Patch Changes

• Updated dependencies [7aa34f6, e7a0a92]:
  • @​tanstack/virtual-core@​3.19.1

3.14.15

Patch Changes

• Updated dependencies [28a2174, 92c697f]:
  • @​tanstack/virtual-core@​3.19.0

3.14.14

Patch Changes

• #1301 ce57b78 - fix(react-virtual): position directDomUpdates rows that mount without the owner re-rendering

  Rows were only positioned by the owner's layout effect or the next onChange. A row mounted by a child that re-renders on its own (local state, context, a resolved Suspense boundary) skipped both when it was fixed-size, and stayed unpositioned until the range changed. Rows are now positioned as they register through measureElement, and containerRef positions the rows that mounted together with the container.

• Updated dependencies [43675bc, 9df47a3, c644f10, 2a631f4]:

  • @​tanstack/virtual-core@​3.18.0

Commits

• 7c20899 ci: Version Packages (#1315)
• cb510cb refactor(virtual-core): describe an in-flight scroll command by one phase (#1...
• 46f73fb ci: Version Packages (#1312)
• 6732e00 test(virtual-core): pin the iOS deferral and index-scroll orderings measured ...
• 84c1502 ci: Version Packages (#1303)
• 92c697f fix(virtual-core): keep lanes aligned after changing lanes with measureElemen...
• 259fc1a ci: Version Packages (#1299)
• 2a631f4 fix(virtual-core): reconcile index scrolls after pending measurements (#1294)
• ce57b78 fix(react-virtual): position directDomUpdates rows that mount without the own...
• See full diff in compare view

Updates i18next from 26.4.2 to 26.4.4

Release notes

Sourced from i18next's releases.

v26.4.4

• fix(security): the nesting regexp no longer backtracks exponentially (ReDoS) on an unclosed $t(. Its repeated group had overlapping alternatives ([^()"']+ inside (?:...)*?, and inside parentheses [^()] also matched quotes), so a string containing $t( without a closing ) made the engine try every way to split the text: about 2x the runtime per extra character, and a ~25 character value hung t() for minutes. With the default config this was reachable through any interpolated value (t('greet', { name: '$t(aaaaaaaaaaaaaaaaaaaaaaaa' })): escaping does not touch $, t or (, and the skipOnVariables check runs the regexp on the interpolated result, so nest: false did not help either. Every alternative now starts with a different character (plain char, ", ' or (), so there is only one way to match and the cost is linear. Quoted strings and one level of parentheses in nesting options keep working (#2336). The only difference: a lone " or ' inside unquoted parentheses within $t(...) is no longer matched. Affects 25.3.3 to 26.4.3. Thanks to Anisetti Chaitanya Eshwar Prasad for the responsible disclosure.
• fix(security): nest() now resolves $t(...) in a single pass and no longer nests text that came out of a resolved value. Every nested lookup reset the shared nesting regexp, so the loop started over from the beginning of the string after each match. That had two effects. First, a $t(...) inside a variable that the nested lookup deliberately kept literal (default skipOnVariables: true) was resolved anyway by the outer loop: with outer: 'A $t(inner) B' and inner: 'Hi {{name}}', t('outer', { name: '$t(secret)' }) rendered the secret translation. It now stays A Hi $t(secret) B, the same as without the outer nesting; with skipOnVariables: false it is still resolved. Second, the cost was quadratic when an unclosed $t( preceded many nestings, which matters when an app passes untrusted input as the key itself (t(userInput)): 20,000 nestings took ~1.4 s, now ~25 ms. The resolved value is now sliced into the result instead of going through String.replace, so $&, $`, $' and $$ stay literal as before (26.4.2).

v26.4.3

• perf: ResourceStore.hasLanguageSomeTranslations() no longer enumerates every key of a large bundle on each call. It ran Object.keys() on the whole bundle just to learn whether it had at least one key, and init() / changeLanguage() reach it three times per instance (once while picking the language, twice via setResolvedLanguage()). With large flat bundles and one i18next instance per SSR request reusing the same resources, that showed up as measurable CPU work before any t() call. Bundle objects already found non-empty are now remembered in a WeakSet shared across instances, so later checks are O(1): 2,000 inits with a 6,800-key bundle went from ~750 ms to ~20 ms, the same as a one-key bundle. Only the non-empty result is cached. No API removes single keys from a bundle, so a non-empty bundle stays non-empty, and empty bundles are re-checked every time, so keys added later (backend loads, addResource, addResourceBundle, direct or silent changes) count right away. The only edge case: a bundle emptied by hand with delete on every key while it is still in the store keeps counting as having translations; use removeResourceBundle() for that. Thanks @​dmchoi77 for the detailed report (#2449).

Changelog

Sourced from i18next's changelog.

26.4.4

• fix(security): the nesting regexp no longer backtracks exponentially (ReDoS) on an unclosed $t(. Its repeated group had overlapping alternatives ([^()"']+ inside (?:...)*?, and inside parentheses [^()] also matched quotes), so a string containing $t( without a closing ) made the engine try every way to split the text: about 2x the runtime per extra character, and a ~25 character value hung t() for minutes. With the default config this was reachable through any interpolated value (t('greet', { name: '$t(aaaaaaaaaaaaaaaaaaaaaaaa' })): escaping does not touch $, t or (, and the skipOnVariables check runs the regexp on the interpolated result, so nest: false did not help either. Every alternative now starts with a different character (plain char, ", ' or (), so there is only one way to match and the cost is linear. Quoted strings and one level of parentheses in nesting options keep working (#2336). The only difference: a lone " or ' inside unquoted parentheses within $t(...) is no longer matched. Affects 25.3.3 to 26.4.3. See advisory GHSA-5jr9-983r-c8x4, CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Thanks to Anisetti Chaitanya Eshwar Prasad for the responsible disclosure.
• fix(security): nest() now resolves $t(...) in a single pass and no longer nests text that came out of a resolved value. Every nested lookup reset the shared nesting regexp, so the loop started over from the beginning of the string after each match. That had two effects. First, a $t(...) inside a variable that the nested lookup deliberately kept literal (default skipOnVariables: true) was resolved anyway by the outer loop: with outer: 'A $t(inner) B' and inner: 'Hi {{name}}', t('outer', { name: '$t(secret)' }) rendered the secret translation. It now stays A Hi $t(secret) B, the same as without the outer nesting; with skipOnVariables: false it is still resolved. Second, the cost was quadratic when an unclosed $t( preceded many nestings, which matters when an app passes untrusted input as the key itself (t(userInput)): 20,000 nestings took ~1.4 s, now ~25 ms. The resolved value is now sliced into the result instead of going through String.replace, so $&, $`, $' and $$ stay literal as before (26.4.2).

26.4.3

• perf: ResourceStore.hasLanguageSomeTranslations() no longer enumerates every key of a large bundle on each call. It ran Object.keys() on the whole bundle just to learn whether it had at least one key, and init() / changeLanguage() reach it three times per instance (once while picking the language, twice via setResolvedLanguage()). With large flat bundles and one i18next instance per SSR request reusing the same resources, that showed up as measurable CPU work before any t() call. Bundle objects already found non-empty are now remembered in a WeakSet shared across instances, so later checks are O(1): 2,000 inits with a 6,800-key bundle went from ~750 ms to ~20 ms, the same as a one-key bundle. Only the non-empty result is cached. No API removes single keys from a bundle, so a non-empty bundle stays non-empty, and empty bundles are re-checked every time, so keys added later (backend loads, addResource, addResourceBundle, direct or silent changes) count right away. The only edge case: a bundle emptied by hand with delete on every key while it is still in the store keeps counting as having translations; use removeResourceBundle() for that. Thanks @​dmchoi77 for the detailed report (#2449).

Commits

• f6a7746 26.4.4
• 25988d5 build
• c9f8eba fix(security): nesting regexp ReDoS on unclosed $t( and single-pass nest(), c...
• 0d2845a 26.4.3
• a2dbe15 build
• e75843f perf: cache non-empty bundles in hasLanguageSomeTranslations, changelog v26.4.3
• edaea71 Fix TypeScript examples build and update them to i18next v26 (#2448)
• 4ebd19d docs: "For AI assistants" paragraph in the README and a fuller saveMissing JSDoc
• See full diff in compare view

Updates react-hook-form from 7.89.0 to 7.90.0

Release notes

Sourced from react-hook-form's releases.

Version 7.90.0

🐞 Fixes

• Fix useForm marking fields named after Object.prototype members as touched on blur and setValue (#13833)
• Fix cloneObject preserving the length of sparse arrays (#13834)
• Fix dirty values extraction for fields named hasOwnProperty (#13832)
• Fix useForm retaining options removed from props on re-render (#13831)
• Fix useFieldArray handling duplicate indexes in remove() without mutating the provided indexes (#13830)
• Fix useFieldArray unregistering fields while a parent array reindexes (#13828)
• Fix input values edited before the form is ready being lost (#13827)
• Fix useWatch not updating watched objects after an Activity subtree reconnects (#13819)
• Fix reset() incorrectly setting isDirty when using keepDefaultValues without values (#13820)
• Fix Controller blur validation not working after reset() (#13817)
• Fix watch using stale shouldUnregister options when registering fields (#13814)
• Fix form value comparison for fields named ref (#13812)
• Fix native validation using stale shouldUseNativeValidation options (#13806)
• Fix cloneObject not cloning objects with a null prototype (#13808)
• Fix useWatch array names not prioritizing form defaultValues (#13805)
• Fix error updates not producing a new errors reference (#13800)
• Fix setError and clearErrors not producing a new errors reference (#13791)

⚡ Performance Improvements

• Improve dirty fields checking (#13788)
• Improve subscription value handling (#13787)
• Improve watch API performance (#13792)
• Improve named scoped subscriptions (#13793)
• Preserve form-state tracking across unsubscribe (#13794)
• Improve subject subscription handling (#13795)
• Skip redundant form-state merges during subscriber notifications (#13796)
• Avoid allocations when matching subscription names (#13823)

🧹 Refactors

• Reduce bundle size (#13797, #13798)
• Clean up tests and fix warnings (#13835)

🧪 Tests

• Add coverage for useFieldArray index boundary and no-op behavior (#13815, #13822, #13824, #13829)
• Add coverage for JSON stringify and parse edge cases (#13821)

📦 Dependencies

• Bump fast-uri from 3.1.2 to 3.1.8 (#13811)
• Bump joi from 18.2.5 to 18.2.6 (#13810)

❤️ Thank You

Thanks to @​charan-rathore, @​zigzagdev, @​AdzerKI, @​huytdps13400, @​dfedoryshchev, @​kory-kaai, @​Mohamed-Elshesheny, @​breken-ai, @​sarmah-rup, @​00200200, @​giaBaoJS and @​bluebill1049 for their contributions! 🎉

Changelog

Sourced from react-hook-form's changelog.

[7.90.0] - 2026-10-10

Changed

• Improve performance of watch, subscribe, scoped subscriptions, dirty field checks and form state fan-out
• Reduce bundle size

Fixed

• Fields named after Object.prototype members not being marked as touched on blur and setValue
• Dirty values extraction for fields named hasOwnProperty
• cloneObject dropping the length of sparse arrays
• cloneObject failing on objects with a null prototype
• Form options removed from props on re-render not being reset
• remove() mishandling duplicated indexes and mutating the indexes passed in
• useFieldArray unregistering fields while a parent array reindexes
• Input edited before the form is ready being overwritten
• useWatch not updating watched objects after an <Activity> subtree reconnects
• useWatch preferring its own defaultValue over form defaultValues for array names
• reset without values and keepDefaultValues setting isDirty to true
• Controller blur validation not working after reset
• watch reading a stale shouldUnregister option when a field registers
• Native validation reading a stale shouldUseNativeValidation option when stopping at the first error
• Form values stored under a ref key not being compared correctly
• setError, clearErrors and remaining error updates not producing a new errors reference

Commits

• 8ac7cc0 7.90.0
• 8f7d2de 🧪 tests cleanup and fix warnings (#13835)
• e76876b 🐞 fix(useForm): mark fields named after Object.prototype members as touched o...
• 08ddcd6 🐞 fix(cloneObject): keep the length of sparse arrays (#13834)
• b8e0a6d 🐞 fix: safely extract dirty values for hasOwnProperty fields (#13832)
• 36e5329 🐞 fix(useForm): reset options that are removed from the props on re-render (#...
• c7cb33a 🐞 fix(useFieldArray): ignore duplicated indexes and keep the indexes passed t...
• 91856c2 🧪 test(swap): cover self-index no-op behavior (#13829)
• 000faaf 🐞 fix(useFieldArray): skip unregister while a parent array reindexes (#13828)
• 7838f08 🐞 fix #13802: keep input edited before the form is ready (#13827)
• Additional commits viewable in compare view

Updates react-i18next from 17.0.15 to 17.0.16

Changelog

Sourced from react-i18next's changelog.

17.0.16

• fix(Trans): a selector i18nKey that points into a secondary namespace of useTranslation now resolves the same way t() does. With const { t } = useTranslation(['ns1', 'ns2']), t($ => $.ns2.message) works since 17.0.7, but <Trans t={t} i18nKey={$ => $.ns2.message} /> rendered the raw key (or its children). Trans always passed an ns option to t, filled from t.ns (the primary namespace only), and an explicit ns makes i18next's fixed t skip the hook's full namespace list (scopeNs). When Trans or TransWithoutContext gets a t that carries its own namespace and no ns prop, it now leaves ns out and lets that t apply its own. String keys, keyPrefix, nsMode: 'fallback', an explicit ns prop and Trans without a t prop behave as before. Compatibility note: if the primary namespace has a nested object named like a secondary namespace (ns1 → ns2.message), Trans now resolves $ => $.ns2.message to ns2:message, as t() already does. Fixes #1933.

Commits

• 606b6a5 17.0.16
• 51b7c26 fix(Trans): resolve selector keys into useTranslation's secondary namespaces
• 0a2f018 fix(examples): load the Swedish file in test-jest and align the ru plural tag...
• See full diff in compare view

Updates react-resizable-panels from 4.14.1 to 4.14.4

Release notes

Sourced from react-resizable-panels's releases.

4.14.4

• Fix pointer events in one document affecting groups mounted in another (e.g. a popup window). The resize cursor is now only shown in the document that contains the active group. - #762
• Fix an error thrown by an onLayoutChange, onLayoutChanged, or onResize callback leaving a drag stuck in the active state or preventing other groups from being updated. The error is now re-thrown once all groups have been updated. - #763

4.14.3

• 761 Bugfix: A drag interrupted by pointercancel, lostpointercapture, or the window losing focus (e.g. Alt/Cmd+Tab) now ends and commits the current layout, rather than staying active until the next pointer event

4.14.2

• 759: Bugfix: Resort panels and separators before (re)deriving constraints

Changelog

Sourced from react-resizable-panels's changelog.

4.14.4

• Fix pointer events in one document affecting groups mounted in another (e.g. a popup window). The resize cursor is now only shown in the document that contains the active group. - #762
• Fix an error thrown by an onLayoutChange, onLayoutChanged, or onResize callback leaving a drag stuck in the active state or preventing other groups from being updated. The error is now re-thrown once all groups have been updated. - #763

4.14.3

• Fix drags interrupted by "pointercancel", "lostpointercapture", or the window losing focus (e.g. Alt/Cmd+Tab) staying active until the next pointer event. The drag now ends and commits the current layout. - #761

4.14.2

• Fix constraints derived from stale panel and separator order by re-sorting them first. - #759

Commits

• b070a13 4.14.3 -> 4.14.4
• cf40d48 Defer errors thrown by layout change callbacks so drags always finish cleanly...
• ada7a21 fix: ignore hit targets from other documents (#762)
• f4c06ad Update CHANGELOG
• 6abc6ac 4.14.2 -> 4.14.3
• 5ac3e5c Bugfix: Handle drags interrupted by "pointercancel", "lostpointercapture", or...
• 8c0573b 4.14.1 -> 4.14.2
• e00997a Bugfix: Resort panels and separators before (re)deriving constraints (#759)
• 7eb8d7a Update react-lib-tools and docs site content
• 8d30dad Update react-lib-tools
• Additional commits viewable in compare view

Updates react-syntax-highlighter from 16.1.1 to 16.1.2

Release notes

Sourced from react-syntax-highlighter's releases.

v16.1.2

What's Changed

• fix: ESM still missing .js with highlight.js by @​Ronny-zzl in react-syntax-highlighter/react-syntax-highlighter#635

New Contributors

• @​Ronny-zzl made their first contribution in react-syntax-highlighter/react-syntax-highlighter#635

Full Changelog: react-syntax-highlighter/react-syntax-highlighter@v16.1.1...v16.1.2

Commits

• 26dbd6c version bump to 16.1.2
• 0c5da9e fix: ESM still missing .js with highlight.js (#635)
• See full diff in compare view

Updates @playwright/test from 1.63.0 to 1.64.0

Release notes

Sourced from @​playwright/test's releases.

v1.64.0

🧰 WebMCP

New page.webmcp and frame.webmcp give access to the tools that a page registers through the experimental WebMCP browser API, so you can test them like any other part of your app:

const browser = await chromium.launch({ args: ['--enable-features=WebMCP'] });
const page = await browser.newPage();
await page.goto('https://example.com');
for (const tool of await page.webmcp.tools())
console.log(tool.name, tool.description);
const result = await page.webmcp.callTool('add', { a: 2, b: 40 });
console.log(result.content[0].text); // "42"

Playwright MCP also supports WebMCP by default, with page-defined tools offered to the agent as webmcp_<tool>. Pass --no-webmcp to opt out.

playwright-cli exposes them as well:

playwright-cli webmcp-list
playwright-cli webmcp-call search_catalog --params '{"query":"cats"}'

🎬 Better videos

Videos can now be recorded at a custom frame rate, and the decorations for actions are styled with plain CSS:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
use: {
video: {
mode: 'on',
size: { width: 1920, height: 1080 },
fps: 60,
show: {
actions: {
style: {
point: 'width: 20px; height: 20px; border-radius: 50%; background: red',
highlight: 'outline: 2px solid #333; background: rgba(0, 128, 255, .15)',
title: 'font-size: 16px',
},
},
},
},
</tr></table>

... (truncated)

Commits

• 606ecd8 cherry-pick(#43192): fix(locators): parse locators the way the client API bui...
• e4f872c cherry-pick(#43188): feat(api): expose asLocatorDescription via LocalUtils fo...
• f6a439e cherry-pick(#43189): docs(webmcp): expose WebMCP to all languages
• e2335c3 cherry-pick(#43174): fix(mcp): do not close the browser twice when the client...
• d2a436e cherry-pick(#43163): Revert "fix(blob): do not remove existing reports from o...
• a0c4b5e cherry-pick(#43175): feat(api): return language-specific locator code from re...
• 3f7d535 cherry-pick(#43131): docs: fix broken C# samples in API docs and handles guide
• 1cde64f cherry-pick(#43170): fix(locators): parse mixed role options
• 8851e72 cherry-pick(#43171): fix(locators): parse JavaScript escapes and regex classes
• dcc5065 cherry-pick(#43172): fix(locator): parse within and getByRef locators
• Additional commits viewable in compare view

Updates @tanstack/eslint-plugin-query from 5.104.0 to 5.104.2

Release notes

Sourced from @​tanstack/eslint-plugin-query's releases.

@​tanstack/eslint-plugin-query@​5.104.2

No changes in this release.

@​tanstack/eslint-plugin-query@​5.104.1

No changes in this release.

Changelog

Sourced from @​tanstack/eslint-plugin-query's changelog.

5.104.2

No changes in this release.

5.104.1

No changes in this release.

Commits

• b699b52 ci: Version Packages (#11849)
• e22e7c4 chore: test TypeScript 7.1 preview and drop 5.6 (#11947)
• df78a9d chore(*): pass the root 'settings' to the package oxlint configs, which 'exte...
• d0cfa6a chore: replace eslint with oxlint (#11938)
• e3415e0 docs(eslint-plugin-query): add JSDoc to the properties of the exported interf...
• f9fe54c docs(eslint-plugin-query): add JSDoc to the exported classes, methods, and ar...
• 847036b docs(eslint-plugin-query): add JSDoc to the exported interfaces and type alia...
• 4736791 docs(*): end JSDoc descriptions with a period and start them with an uppercas...
• cbdb214 docs(*): replace JSDoc descriptions that only repeat the names and enforce 'j...
• fe30a84 docs(eslint-plugin-query): add missing JSDoc to rule helpers and utilities (#...
• Additional commits viewable in compare view

Updates @types/node from 26.6.3 to 26.6.5

Commits

• See full diff in compare view

Updates @vitejs/plugin-react from 6.1.1 to 6.1.2

Release notes

Sourced from @​vitejs/plugin-react's releases.

plugin-react@6.1.2

Fix HMR for compound components (#1484)

Adding or removing a component from a compound component was not handled, creating stale updates. Doing this now triggers hmr invalidate on the file and propagates the invalidation to importers.

Fix compiler.logDiagnostics option not working (#1483)

With oxc-transform-react >= 0.148, the logDiagnostics was not working. This version fixes it and requires oxc-transform-react >= 0.152 as a peer dependency if you are using the compiler option. compiler.logDiagnostics option is now deprecated and should be swapped for the builtin compiler.reportDiagnostics.

Disable refresh for non-jsx with compiler enabled (fix #1478) (#1485)

When the compiler was enabled, TS files could trigger fast refresh which would cause runtime errors. The logic now follows what the builtin oxc plugin in Vite does.

Changelog

Sourced from @​vitejs/plugin-react's changelog.

6.1.2 (2026-10-05)

Fix HMR for compound components (#1484)

Adding or removing a component from a compound component was not handled, creating stale updates. Doing this now triggers hmr invalidate on the file and propagates the invalidation to importers.

Fix compiler.logDiagnostics option not working (#1483)

With oxc-transform-react >= 0.148, the logDiagnostics was not working. This version fixes it and requires oxc-transform-react >= 0.152 as a peer dependency if you are using the compiler option. compiler.logDiagnostics option is now deprecated and should be swapped for the builtin compiler.reportDiagnostics.

Disable refresh for non-jsx with compiler enabled (fix #1478) (#1485)

When the compiler was enabled, TS files could trigger fast refresh which would cause runtime errors. The logic now follows what the builtin oxc plugin in Vite does.

Commits

• ac47648 release: plugin-react@6.1.2 (#1491)
• 98277e7 fix(deps): update all non-major dependencies (#1486)
• 12eddea fix(hmr): better handle compound components (#1484)
• 3cfb1d1 fix(plugin-react): fix compiler.logDiagnostics (#1483)
• 6de9915 fix(plugin-react): disable refresh for non-jsx with compiler enabled (#1485)
• ee97d2f fix(deps): update all non-major dependencies (#1445)
• b0a014d chore: use Babel 8 for babel compiler playgrounds (#1460)
• 61b650f fix(deps): update react-related dependencies (#1452)
• 736efe2 chore(deps): update tsdown to v0.23 (#1451)
• See full diff in compare view

Updates @vitest/coverage-v8 from 5.0.3 to 5.0.4

Release notes

Sourced from @​vitest/coverage-v8's releases.

v5.0.4

   🚀 Features

• experimental:
  • Tag cache directories with CACHEDIR.TAG  -  by @​lifeiscontent in vitest-dev/vitest#11461 (a8ea3)
  • Support test.ui.theme option  -  by @​sheremet-va in vitest-dev/vitest#11499