-
Notifications
You must be signed in to change notification settings - Fork 165
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
An in-range update of eslint-plugin-react is breaking the build 🚨 #558
Comments
After pinning to 7.14.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 30 commits.
There are 30 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 4 commits.
See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v7.17.0Added
Fixed
Changed
CommitsThe new version differs by 26 commits.
There are 26 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 32 commits.
There are 32 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
The devDependency eslint-plugin-react was updated from
7.14.2
to7.14.3
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Release Notes for v7.14.3
Fixed
prop-types
to ignore validation when Flow indexers are used (#2330 @yannickcr)memo
andforwardRef
are used together (#2349 @yannickcr)Changed
Commits
The new version differs by 14 commits.
47c4c8b
Update CHANGELOG and bump version
98d4bf3
Fix component detection when memo and forwardRef are used together
fc70077
Merge pull request #2354 from golopot/patch-1
f2891d9
[docs] remove outdated docs for
no-unused-prop-types
49343d4
[meta] add github sponsorship
562e441
Add Tidelift badge to README
b684e87
Add SECURITY file
22a3740
Add FUNDING file
e835aaf
add note about global installs being deprecated
0215c38
Merge pull request #2336 from abhishekdev/handle-react-detect-errors
8fbf50c
version detection: Do not throw a raw error after the first warning
f59e927
version detection: Add tests
d6832d6
Fix new required import order
bc67d42
Fix prop-types to ignore validation when Flow indexers are used
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: