• Fix: Notify framework when count changes to update getTotalSize() (#1085)

  Fixed an issue where getTotalSize() would return stale values when the count option changed (e.g., during filtering or search operations). The virtualizer now automatically notifies the framework when measurement-affecting options change, ensuring the UI updates correctly without requiring manual useMemo workarounds.

  Before: When filtering items, the list container would maintain its previous height, causing excessive blank space (when count decreased) or inaccessible items (when count increased).

  After: Height updates automatically when count changes, providing the correct user experience.

  This fix applies to all framework adapters and has minimal performance impact (< 0.1ms per change).

• Updated dependencies [2542c5a, 96e32a6]:

  • @tanstack/virtual-core@3.13.13

• Fix: Notify framework when count changes to update getTotalSize() (#1085)

  Fixed an issue where getTotalSize() would return stale values when the count option changed (e.g., during filtering or search operations). The virtualizer now automatically notifies the framework when measurement-affecting options change, ensuring the UI updates correctly without requiring manual useMemo workarounds.

  Before: When filtering items, the list container would maintain its previous height, causing excessive blank space (when count decreased) or inaccessible items (when count increased).

  After: Height updates automatically when count changes, providing the correct user experience.

  This fix applies to all framework adapters and has minimal performance impact (< 0.1ms per change).

• fix: stabilize lane assignments in masonry layout (#1080)

  Added lane assignment caching to prevent items from jumping between lanes when viewport is resized. Previously, items could shift to different lanes during resize due to recalculating "shortest lane" with slightly different heights.

  Changes:

  • Added laneAssignments cache (Map<index, lane>) to persist lane assignments
  • Lane cache is cleared when lanes option changes or measure() is called
  • Lane cache is cleaned up when count decreases (removes stale entries)
  • Lane cache is cleared when virtualizer is disabled

• Fix: Notify framework when count changes to update getTotalSize() (#1085)

  Fixed an issue where getTotalSize() would return stale values when the count option changed (e.g., during filtering or search operations). The virtualizer now automatically notifies the framework when measurement-affecting options change, ensuring the UI updates correctly without requiring manual useMemo workarounds.

  Before: When filtering items, the list container would maintain its previous height, causing excessive blank space (when count decreased) or inaccessible items (when count increased).

  After: Height updates automatically when count changes, providing the correct user experience.

  This fix applies to all framework adapters and has minimal performance impact (< 0.1ms per change).

• Updated dependencies [2542c5a, 96e32a6]:

  • @tanstack/virtual-core@3.13.13

• Fix: Notify framework when count changes to update getTotalSize() (#1085)

  Fixed an issue where getTotalSize() would return stale values when the count option changed (e.g., during filtering or search operations). The virtualizer now automatically notifies the framework when measurement-affecting options change, ensuring the UI updates correctly without requiring manual useMemo workarounds.

  Before: When filtering items, the list container would maintain its previous height, causing excessive blank space (when count decreased) or inaccessible items (when count increased).

  After: Height updates automatically when count changes, providing the correct user experience.

  This fix applies to all framework adapters and has minimal performance impact (< 0.1ms per change).

• Updated dependencies [2542c5a, 96e32a6]:

  • @tanstack/virtual-core@3.13.13

• Fix: Notify framework when count changes to update getTotalSize() (#1085)

  Fixed an issue where getTotalSize() would return stale values when the count option changed (e.g., during filtering or search operations). The virtualizer now automatically notifies the framework when measurement-affecting options change, ensuring the UI updates correctly without requiring manual useMemo workarounds.

  Before: When filtering items, the list container would maintain its previous height, causing excessive blank space (when count decreased) or inaccessible items (when count increased).

  After: Height updates automatically when count changes, providing the correct user experience.

  This fix applies to all framework adapters and has minimal performance impact (< 0.1ms per change).

• Updated dependencies [2542c5a, 96e32a6]:

  • @tanstack/virtual-core@3.13.13

• Fix: Notify framework when count changes to update getTotalSize() (#1085)

  Fixed an issue where getTotalSize() would return stale values when the count option changed (e.g., during filtering or search operations). The virtualizer now automatically notifies the framework when measurement-affecting options change, ensuring the UI updates correctly without requiring manual useMemo workarounds.

  Before: When filtering items, the list container would maintain its previous height, causing excessive blank space (when count decreased) or inaccessible items (when count increased).

  After: Height updates automatically when count changes, providing the correct user experience.

  This fix applies to all framework adapters and has minimal performance impact (< 0.1ms per change).

• Updated dependencies [2542c5a, 96e32a6]:

  • @tanstack/virtual-core@3.13.13

• Fix: Notify framework when count changes to update getTotalSize() (#1085)

  Fixed an issue where getTotalSize() would return stale values when the count option changed (e.g., during filtering or search operations). The virtualizer now automatically notifies the framework when measurement-affecting options change, ensuring the UI updates correctly without requiring manual useMemo workarounds.

  Before: When filtering items, the list container would maintain its previous height, causing excessive blank space (when count decreased) or inaccessible items (when count increased).

  After: Height updates automatically when count changes, providing the correct user experience.

  This fix applies to all framework adapters and has minimal performance impact (< 0.1ms per change).

• Updated dependencies [2542c5a, 96e32a6]:

  • @tanstack/virtual-core@3.13.13

This bugfix release fixes an issue with our internal AbortSignal handling that was reported as causing an error in a rare reset situation. We've also restructured our publishing process to use NPM Trusted Publishing, and updated our TS support matrix to only support TS 5.4+.

We've previously done most of our releases semi-manually locally, with various release process CLI tools. With the changes to NPM publishing security and the recent wave of NPM attacks, we've updated our publishing process to solely use NPM Trusted Publishing via workflows. We've also done a hardening pass on our own CI setup.

We had done a couple releases via CI workflows previously, and later semi-manual releases caused PNPM to warn that RTK was no longer trusted. This release should be trusted and will resolve that issue.

Thanks to the e18e folks and their excellent guide at https://e18e.dev/docs/publishing for making this process easier!

We've previously mentioned rolling changes to our TS support matrix in release notes, but didn't officially document our support policy. We've added a description of the support policy (last 2 years of TS releases, matching DefinitelyTyped) and the current oldest TS version we support in the docs:

• https://redux-toolkit.js.org/introduction/getting-started#typescript
• https://redux-toolkit.js.org/usage/usage-with-typescript#introduction

As of today, we've updated the support matrix to be TS 5.4+ . As always, it's possible RTK will work if you're using an earlier version of TS, but we don't test against earlier versions and don't support any issues with those versions.

We have run an initial test with the upcoming TS 7.0 native tsgo release. We found a couple minor issues with our own TS build and test setup, but no obvious issues with using RTK with TS 7.0.

A user reported a rare edge case where the combination of resetApiState and retry() could lead to an error calling an AbortController. We've restructured our AbortController handling logic to avoid that (and simplified a bit of our internals in the process).

• Use trusted publishing and harden workflows by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/5152
• Update TS typecheck matrix and add TS native job by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/5155
• Officially document TS support by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/5158
• Tweaks to AbortSignal logic by @EskiMojo14 in https://github.com/reduxjs/redux-toolkit/pull/5150

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.11.0...v2.11.1

Please refer to CHANGELOG.md for details.

This feature release adds new RTKQ codegen config options for outputting regex constants when the pattern keyword is used in an OpenAPI definition, and defining explicit tag overrides on a per-endpoint basis as part of the codegen config.

• feat: (codegen) output regex patterns for generated schemas by @RhysOnlyBetter in https://github.com/reduxjs/redux-toolkit/pull/5146
• feat(codegen): support explicit tag overrides without altering defaults by @w3di in https://github.com/reduxjs/redux-toolkit/pull/5135
• Add test for #3369 by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/5154

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/@rtk-query/codegen-openapi@2.1.0...@rtk-query/codegen-openapi@2.2.0