Update dependency react-redux to v9.3.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
react-redux	9.1.1 → 9.3.0

---

Release Notes

reduxjs/react-redux (react-redux)

v9.3.0

Compare Source

This feature release officially marks the connect API as deprecated.

That's it. That's the release. :)

Changelog

connect deprecation

Way back in 2022, I officially marked the original Redux core createStore method as deprecated in Redux 4.2.0. As I clearly stated in that release, the goal of marking createStore as deprecated was to encourage users to migrate to modern Redux Toolkit, especially for those users who don't read our docs (such as beginners following outdated tutorials or in bootcamps, etc). The change was visual-only - adding @deprecated just marks the import with a strikethrough in an IDE, and the docblock references the "use modern Redux Toolkit" docs page. No runtime errors, no behavior changes, just an indication that the function is considered obsolete and you shouldn't use it directly any more. I also exported a legacy_createStore alias - same function, no deprecation attribute.

It's 4 years later, and I'm finally doing the same thing for connect :)

Again, nothing about connect's behavior is changing, and we do not intend to remove the connect API. But it's 2026, and hooks are the correct way to use React and React-Redux today.

We do strongly encourage users to migrate from connect to the useSelector / useDispatch hooks in general. This should result in codebases that are easier to understand and ought to improve performance slightly due to the way updates are handled.

As with before, React-Redux now exports a legacy_connect alias that does not have the deprecation attribute applied.

Trusted Publishing Fixed

We had set up trusted publishing for React-Redux a couple years ago and did some releases with that enabled, but at some point I did a follow-up release that still used the previous manual workflow, and that lost the trusted publishing provenance flag. We had recent issues requesting a new release with trusted publishing enabled again, so we've fixed that with this release.

What's Changed

• Mark connect as deprecated by @​markerikson in #​2269

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

v9.2.0

Compare Source

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 #​2176
• Migrate to React by @​aryaemami59 in #​2172
• Migrate to React 19 (take 2) by @​markerikson in #​2216
• Clean up devdeps by @​markerikson in #​2217

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

v9.1.2

Compare Source

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 #​2164
• Replace usage of deprecated JSX global namespace with React.JSX by @​aryaemami59 in #​2163
• Drop now-unneeded RN peer dep by @​markerikson in #​2167
• Fix remaining React 19 types issues by @​markerikson in #​2168

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
standup-timer	Ready	Preview, Comment	May 15, 2026 6:03pm