Closed greenkeeper[bot] closed 3 years ago
After pinning to 7.1.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
dependency
react-redux was updated from 7.1.1
to 7.1.2
.Your tests are still failing with this version. Compare changes
This releases fixes a subtle timing bug with connect
and useSelector
in React Native environments, and adds the ability to pass through non-Redux-store values as a store
prop.
Our current implementation requires cascading updates down through connected components. This is primarily done during React's "commit phase" via the useLayoutEffect
hook. Unfortunately, React warns when useLayoutEffect
is called in SSR environments, so we try to feature-detect that and fall back to useEffect
just to avoid that warning.
Unfortunately, a tweak to the feature detection conditions during the pre-7.1.0 work caused the check to accidentally fail in React Native environments. This meant that useEffect
was actually being used all the time, and this led to occasional timing bugs such as #1313 and #1437 . This affected the previous v7.1.x releases.
We've fixed that issue, and added additional test cases to ensure that our code works correctly under React Native.
See #1444 for more details on the feature detection and the fix.
connect
has always accepted passing a Redux store directly to connected components as a prop named store
(with the exception of v6). As a result, the store
prop has effectively been treated as a "reserved" prop, in much the same way that key
and ref
are "reserved" prop names handled by React.
Some users may be using the word "store" to describe their domain data, and have asked to allow variables that aren't a Redux store through the store
prop to the component (#1393). We've finally been able to implement that capability.
store
prop (@markerikson - #1447)latestStoreState
field (@Hypnosphi - #1426)dependency
react-redux was updated from 7.1.3
to 7.2.0
.Your tests are still failing with this version. Compare changes
The new version differs by 37 commits.
ec38c1b
7.2.0
fa5a7fd
Fix memory leak issue with UseEffect
(#1506)
e649fb6
Optimize createListenerCollection (#1523)
3eb5271
Updated links (#1522)
b3db96c
docs: mapDispatchToProps returning undefined (#1520)
607f1ba
Fix: Fix typo in connect.md (#1517)
77a2044
Remove these spaces.
cff554d
Update connect-dispatching-actions-with-mapDispatchToProps.md (#1501)
9a10b15
Update hooks.md (#1405)
7893b35
Fixed Q&A links (#1500)
b3ae892
Fixes broken links (#1494)
f9efe46
fix: correct link to Redux Troubleshooting page (#1493)
863128e
Fix Usage with React link.
19359fb
remove useless semicolon (#1486)
67d5e86
Add Netlify Badge to Docs (#1485)
There are 37 commits in total.
See the full diff
dependency
react-redux was updated from 7.0.3
to 7.1.0
.Your tests are passing again with this update. Explicitly upgrade to this version π
After much discussion, we've decided these Hook things are probably going to stick around, so we might as well add some. Many thanks to @MrWolfZ, @josepot, @perrin4869, and @mpeyper for their contributions and to everyone else that offered feedback, ideas, and critiques as we built them out. Go open source!
deps
argument to useSelector
(#1251 by @MrWolfZ)useRedux
(@markerikson)useActions
(@markerikson)deps
argument (#1272 by @josepot)shallowEqual
with reference equality in useSelector
(#1288 by @perrin4869)
The dependency react-redux was updated from
7.1.2
to7.1.3
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
react-redux is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- β **ci/circleci: build:** Your tests passed on CircleCI! ([Details](https://circleci.com/gh/alpersonalwebsite/react-redux-example-redux-thunk/78?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)). - β **WhiteSource Security Check:** The Security Check found 3 vulnerabilities.| Severity | CVSS Score |CVE | GitHub Issue | | ------------- |-------------|-----|------| | Medium | 6.1 | [CVE-2015-9251](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9251 "Go to CVE Details") | [#15](https://github.com/alpersonalwebsite/react-redux-example-redux-thunk/issues/15 "Go to GitHub Issue") | Medium | 6.1 | [CVE-2012-6708](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-6708 "Go to CVE Details") | [#14](https://github.com/alpersonalwebsite/react-redux-example-redux-thunk/issues/14 "Go to GitHub Issue") | Medium | 4.3 | [WS-2016-0090](https://github.com/jquery/jquery/commit/b078a62013782c7424a4a61a240c23c4c0b42614 "Go to CVE Details") | [#16](https://github.com/alpersonalwebsite/react-redux-example-redux-thunk/issues/16 "Go to GitHub Issue") Scan token: 16e15ec892a340dcb54fe085117fd333
Release Notes for v7.1.3
Forgot to remove a
console
statement before publish 7.1.2. Oops!Lint your source code before publishing, folks.
Changelog
v7.1.2...v7.1.3
Commits
The new version differs by 2 commits.
82b39ef
7.1.3
30101bb
Remove leftover console statement
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donβt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: