-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Data: upgrade Redux to v5.0.1 #66966
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Size Change: -282 B (-0.02%) Total Size: 1.82 MB
ℹ️ View Unchanged
|
Mamaduka
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just skimmed the Redux release notes and couldn't spot anything breaking that might affect the block editor code base.
It looks like createStore has been marked as deprecated since 4.2. Should we switch to legacy_createStore to make current intentions clear? I'm not sure it's doable for this project to migrate to RTK.
Maybe, but I don't think it's particularly important. A striked-out
Agreed, in a sense |
|
Flaky tests detected in ac2fea2. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11818428875
|
|
I always forget about changelogs, but it could be helpful in this case - #66968. |
Let's upgrade Redux to the latest version 5.0.1. There are apps that use both
@wordpress/dataand plainreduxand the fact that we still use the old 4.x version causes unnecessarynode_modulesconflicts.There shouldn't be any visible changes, after all, the
reduxAPI surface is very small. Maybe only the TS types might have some incompatible changes, but I don't see any.