An in-range update of eslint is breaking the build 🚨
Closed this issue · 2 comments
Version 3.13.1 of eslint just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | eslint |
| Current Version | 3.13.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
v3.13.1Commits
The new version differs by 4 commits .
7f8393c3.13.191883bfBuild: package.json and changelog update for 3.13.13fc4e3fFix: prefer-destructuring reporting compound assignments (fixes #7881) (#7882)f90462eFix: no-extra-label autofix should not remove labels used elsewhere (#7885)
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
After pinning to 3.13.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Fixed (by adding a travis config)