chore(deps): bump @reduxjs/toolkit from 1.9.5 to 2.11.2

[dependabot]

Bumps @reduxjs/toolkit from 1.9.5 to 2.11.2.

Release notes

Sourced from @​reduxjs/toolkit's releases.

v2.11.2

This bugfix release updates the AbortSignal handling to fall back if DOMException isn't available (such as RN environments), and updates the TypedUseInfiniteQueryHookResult type to correctly include fetchNextPage/fetchPreviousPage fields.

Changelog

Bugfixes

The AbortSignal changes in 2.11.1 used DOMException in a couple places to match the expected behavior of AbortSignal, but turns out that's not available in environments like React Native. We've updated the logic to fall back to a plain Error if DOMException isn't available.

The TypedUseInfiniteQueryHookResult type wasn't correctly including the fetchNextPage/fetchPreviousPage fields, and now it does.

What's Changed

• fix: use a normal Error when DOMException isn't available by @​EskiMojo14 in reduxjs/redux-toolkit#5161
• Include page functions in TypedUseInfiniteQueryHookResult by @​markerikson in reduxjs/redux-toolkit#5165

Full Changelog: reduxjs/redux-toolkit@v2.11.1...v2.11.2

v2.11.1

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+.

Changelog

Publishing Changes

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!

TS Support Matrix Updates

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.

Bug Fixes

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).

What's Changed

• Use trusted publishing and harden workflows by @​markerikson in reduxjs/redux-toolkit#5152

... (truncated)

Commits

• 646d54c Release 2.11.2
• 819b29c Include page functions in TypedUseInfiniteQueryHookResult (#5165)
• 9af97ca fix: use a normal Error when DOMException isn't available (#5161)
• 3615d1a Merge pull request #5120 from reduxjs/vitest-bumps
• fae3b95 avoid excessive type instantiation
• d296e33 fix type issue with RTKQ and reselect
• 9ce71b9 add node to types field
• d14d427 remove unused tests
• 324dd05 bump vite to match
• b0887c4 bump to vitest v4
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​reduxjs/toolkit since your current version.

---

Note

Medium Risk
This is a major-version upgrade of Redux Toolkit that also pulls in redux@5, redux-thunk@3, reselect@5, and immer@11, which can introduce subtle runtime/type changes in state management.

Overview
Upgrades @reduxjs/toolkit from ^1.6.2 (resolved 1.9.5) to ^2.11.2.

Updates yarn.lock to the new dependency tree, including newer redux, redux-thunk, reselect, and immer, and adds @standard-schema/spec and @standard-schema/utils required by RTK v2.

^{Reviewed by Cursor Bugbot for commit 822a026. Bugbot is set up for automated code reviews on this repo. Configure here.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[jit-ci]

🛡️ Jit Security Scan Results

✅ No security findings were detected in this PR

---

^{Security scan by Jit}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 44af374. Configure here.}

[cursor]

redux-thunk v3 removes default export, breaking test infrastructure

High Severity

Bumping @reduxjs/toolkit to v2 pulls in redux-thunk v3, which removed its default export. The codebase uses import thunk from 'redux-thunk' in test-utils.tsx and rejson.setJsonDataAction.spec.ts. With v3, thunk will be undefined, causing configureMockStore([undefined]) to silently produce a broken mock store that can't handle async actions, failing the entire test suite.

Additional Locations (1)

• yarn.lock#L13227-L13231

 

^{Reviewed by Cursor Bugbot for commit 44af374. Configure here.}

[cursor]

react-redux v7 incompatible with Redux 5 from RTK 2

High Severity

The project uses react-redux@^7.2.2 which has a peer dependency on redux@^2 || ^3 || ^4. This RTK 2 upgrade pulls in redux@5.0.1, creating an unsupported combination. The store created by configureStore uses Redux 5 internals, but react-redux v7 expects a Redux 4 store, likely causing TypeScript failures and potential runtime incompatibilities. The official migration guide requires upgrading to react-redux@9.

Additional Locations (1)

• yarn.lock#L13239-L13243

 

^{Reviewed by Cursor Bugbot for commit 44af374. Configure here.}