[Snyk] Upgrade react-redux from 7.1.3 to 7.2.9 #84
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade react-redux from 7.1.3 to 7.2.9.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version fixes:
SNYK-JS-UAPARSERJS-1023599
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-ES5EXT-6095076
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-INI-1048974
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-LODASH-1040724
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-LODASH-567746
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-LODASH-608086
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-SEMVER-3247795
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-SHELLQUOTE-1766506
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-TAR-1536528
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-TAR-1536531
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-TAR-1579147
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-TAR-1579152
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-TAR-1579155
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-UAPARSERJS-610226
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-MINIMIST-559764
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-MINIMIST-559764
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-NODEADDONAPI-571001
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-NODEFETCH-2342118
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-NODEFETCH-674311
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-NODEFETCH-2342118
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-NODEFETCH-674311
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-NODEFETCH-2342118
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-COLORSTRING-1082939
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-LODASH-1018905
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-MINIMATCH-3050818
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-NODEFETCH-674311
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-REACTDEVTOOLSCORE-6023999
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-UAPARSERJS-1072471
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-WS-1296835
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-MINIMIST-2429795
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-MINIMIST-2429795
Why? Proof of Concept exploit, CVSS 7.5
SNYK-JS-TAR-1536758
Why? Proof of Concept exploit, CVSS 7.5
npm:debug:20170905
Why? Proof of Concept exploit, CVSS 7.5
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: react-redux
This patch release updates the rarely-used
areStatesEqual
option forconnect
to now pass throughownProps
for additional use in determining which pieces of state to compare if desired.The new signature is:
What's Changed
Full Changelog: v7.2.8...v7.2.9
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 auseLayoutEffect
instead of auseMemo
. 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: v7.2.7...v7.2.8
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.
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs