Update dependency react-redux to v7.2.8

[matticbot]

This PR contains the following updates:

Package	Type	Update	Change
react-redux	dependencies	patch	7.2.6 -> 7.2.8
@types/react-redux	devDependencies	patch	7.1.23 -> 7.1.24

---

Release Notes

reduxjs/react-redux

v7.2.8

Compare Source

This release fixes a bug in the 7.x branch that caused <Provider> to unsubscribe and stop updating completely when used inside of React 18's <StrictMode>. The new "strict effects" behavior double-mounts components, and the subscription needed to be set up inside of a useLayoutEffect instead of a useMemo. This was previously fixed as part of v8 development, and we've backported it.

Note: If you are now using React 18, we strongly recommend using the React-Redux v8 beta instead of v7.x!. v8 has been rewritten internally to work correctly with React 18's Concurrent Rendering capabilities. React-Redux v7 will run and generally work okay with existing code, but may have rendering issues if you start using Concurrent Rendering capabilities in your code.

Now that React 18 is out, we plan to finalize React-Redux v8 and release it live within the next couple weeks. Per an update yesterday in the "v8 roadmap" thread, React-Redux v8 will be updated in the next couple days to ensure support for React 16.8+ as part of the next beta release. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version.

Full Changelog: reduxjs/react-redux@v7.2.7...v7.2.8

v7.2.7

Compare Source

This release updates React-Redux v7's peer dependencies to accept React 18 as a valid version, only to avoid installation errors caused by NPM's "install all the peer deps and error if they don't match" behavior.

Note: If you are now using React 18, we strongly recommend using the React-Redux v8 beta instead of v7.x!. v8 has been rewritten internally to work correctly with React 18's Concurrent Rendering capabilities. React-Redux v7 will run and generally work okay with existing code, but may have rendering issues if you start using Concurrent Rendering capabilities in your code.

Now that React 18 is out, we plan to finalize React-Redux v8 and release it live within the next couple weeks. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version.

---

Configuration

📅 Schedule: "before 3am on the first day of the month" in timezone UTC.

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

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

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

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Renovate Bot.

[matticbot]

Caution: This PR has changes that must be merged to WordPress.com
Hello matticbot! These changes need to be synced to WordPress.com - If you 're an a11n, please commandeer and confirm D80406-code works as expected before merging this PR. Once this PR is merged, please commit the changes to WP.com. Thank you!
This revision will be updated with each commit to this PR

Not much point if we don't update jetpack's dep on v6.0.1 too

[anomiex]

I'd like a second set of eyes on the d0c482d part.

[samiff]

The redux change looks ok to me, and I tested that I could see a <JetpackBanner> upgrade banner working as expected.

[github-actions]

Great news! One last step: head over to your WordPress.com diff, D80406-code, and deploy it.
Once you've done so, come back to this PR and add a comment with your changeset ID.

Thank you!

[anomiex]

r245605-wpcom

[markerikson]

Hi! I'm a Redux maintainer. Out of curiosity, what's the need to use the alternate-renderers entry point in this update?

[anomiex]

Hi @markerikson!

Based on b5c2352, it seems that at the time there was some sort of conflict between the new version of react-redux (updating from 6.0.1 to 7.2.8) and static-site-generator-webpack-plugin that caused webpack to hang instead of exiting. I don't recall where I got the idea to use the alternate-renderers entry point to fix that, but I see if I check out 9854a7b and try to build it still hangs.

On the other hand, if I remove the alias from our current trunk it seems to no longer hang. Bisect points to #28710 as when alternate-renderers was no longer needed.

[markerikson]

@anomiex : gotcha, thanks for the update! I'm still planning on having an /alternate-renderers entry point in React-Redux v9, but was searching around to see how much it's used first. Honestly there's only a handful of usages I can find, and this one stood out as being a bit unusual.