Skip to content
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 🚨 #52

Closed
greenkeeper bot opened this issue Jan 16, 2019 · 2 comments
Closed

An in-range update of eslint-plugin-react is breaking the build 🚨 #52

greenkeeper bot opened this issue Jan 16, 2019 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jan 16, 2019

The devDependency eslint-plugin-react was updated from 7.12.2 to 7.12.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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v7.12.3

Fixed

Changed

Commits

The new version differs by 14 commits.

  • 2f5cec9 Update CHANGELOG and bump version
  • 096161a Merge pull request #2120 from jomasti/issue-2119
  • 9d3955a Prevent crash of jsx-indent rule
  • 230c7e0 Merge pull request #2117 from haideralsh/patch-1
  • b4b0e72 fix: add a missing in the JSON settings
  • d2aa260 Merge pull request #2115 from drx/class_body_prop_types
  • 41974e5 Fix propType detection inside class bodies
  • 40f2565 [Docs] update README to document React version detection
  • dd0757f Merge pull request #2113 from alexzherdev/2112-fix-self-closing-fragments
  • e997f6c [Fix] avoid crashing on self-closing fragments
  • b48b479 Merge pull request #2111 from drx/prop_types_class_properties
  • e15bafa [Fix] no-unused-prop-types: fix issue with propTypes misclassifying props
  • a86b339 Merge pull request #2109 from jomasti/issue-2105
  • 5f9863e Fix display-name false positive for React.memo

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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jan 16, 2019

After pinning to 7.12.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jan 17, 2019

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for v7.12.4

Fixed

Changed

Commits

The new version differs by 10 commits.

  • 433cc3f Update CHANGELOG and bump version
  • 536bc35 [Tests] prop-types: add case from #2134
  • df7ffc1 [Tests] no-typos: test case from #2136
  • c7e5f38 [Tests] improve version detection tests.
  • 2dd2277 [Tests] prop-types: add now-passing test case
  • 84652b6 [Fix] no-unused-prop-types: avoid a crash
  • 58ed9e9 [Fix] prop-types: avoid further crashes from nonexistent nodes in unusedPropTypes
  • 7f7b96d [Fix] prop-types: Read name of callee object.
  • 5fc50aa [Fix] Ignore reassignments when matching props declarations with components
  • ba80a4c [Fix] Detect components with return statement in switch/case

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant