build(deps): bump the redux group in /web-app with 2 updates

[dependabot]

Bumps the redux group in /web-app with 2 updates: @reduxjs/toolkit and react-redux.

Updates @reduxjs/toolkit from 1.9.7 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](https://www.npmjs.com/~GitHub Actions), a new releaser for @​reduxjs/toolkit since your current version.

Updates react-redux from 8.1.3 to 9.2.0

Release notes

Sourced from react-redux's releases.

v9.2.0

This feature release updates the React peer dependency to work with React 19, and improves treeshakeability of our build artifacts.

Changelog

React 19 Compat

React 19 was just released! We've updated our peer dep to accept React 19, and updated our runtime and type tests to check against both React 18 and 19.

Also see Redux Toolkit v2.5.0 for the same peer dep update.

Treeshaking

We've done some nitty-gritty optimization work to ensure bundlers correctly treeshake unused parts of the bundle.

What's Changed

• Improve treeshakeability of build artifacts by @​aryaemami59 in reduxjs/react-redux#2176
• Migrate to React by @​aryaemami59 in reduxjs/react-redux#2172
• Migrate to React 19 (take 2) by @​markerikson in reduxjs/react-redux#2216
• Clean up devdeps by @​markerikson in reduxjs/react-redux#2217

Full Changelog: reduxjs/react-redux@v9.1.2...v9.2.0

v9.1.2

This bugfix release removes the no-longer-necessary peer dependency on react-native, and tweaks a few TS types for compat with the upcoming React 19 release.

Changes

React Native Peer Dependency Removed

We've always had an awkward peer dependency on both ReactDOM and React Native, because of the need to import the unstable_batchedUpdates API directly from each reconciler. That's part of what led to the sequence of 9.x patch releases to deal with RN compat.

As of 9.0.3, we dropped the batching imports completely, since React 18 now batches by default. That means we didn't even have any remaining imports from react-native.

Meanwhile, React 18.3 just came out, but so did React Native 0.74. RN 0.74 still requires React 18.2.

This caused NPM users to have installation failures when trying to use React-Redux:

• React-Redux has a peer dep on RN
• RN has a peer dep on React 18.2
• But the latest React, 18.3 would get installed in the app
• NPM errors with a peer dep mismatch

We no longer need to list RN as a peer dep, and dropping that also fixes the NPM installation issues as well.

What's Changed

• Fix useRef usages to be called with an explicit argument of undefined. by @​aryaemami59 in reduxjs/react-redux#2164

... (truncated)

Commits

• 7e2fdd4 Release 9.2.0
• 8c57382 Merge pull request #2217 from reduxjs/feature/react-19-devdep-cleanup
• d23509b Exclude stray dist folders and website from tsconfig
• b275a32 Eliminate other stray React import
• 3ba9838 Drop unused Babel devdeps
• 1a81c41 Merge pull request #2216 from reduxjs/migrate-to-react-19
• c58e397 Migrate to React 19
• e08518a Fix act related issues in test/hooks/useSelector.spec.tsx
• 1cd1385 Update hoist-non-react-statics implementation
• a1fc886 Fix type of innerMapStateToProps in Provider.spec.tsx
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions