-
Notifications
You must be signed in to change notification settings - Fork 24
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 is breaking the build 🚨 #82
Comments
After pinning to 5.12.0 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 Release Notes for v5.13.0
CommitsThe new version differs by 13 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v5.14.1CommitsThe new version differs by 41 commits.
There are 41 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v5.15.0
CommitsThe new version differs by 63 commits.
There are 63 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v5.15.1CommitsThe new version differs by 67 commits.
There are 67 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v5.15.2
CommitsThe new version differs by 19 commits.
There are 19 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v5.16.0
CommitsThe new version differs by 15 commits.
See the full diff |
The devDependency eslint was updated from
5.12.0
to5.12.1
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
eslint 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 v5.12.1
eb5c401
Chore: use meta.messages in some rules (2/4) (refs #9870) (#10773) (薛定谔的猫)aa56247
Fix: avoid loading core rules dynamically from FS in Linter (#11278) (Peter Metz)04450bb
Docs: clarify process for adding committers (#11272) (Kai Cataldo)3ffcf26
Docs: add @g-plane as committer (#11277) (Kai Cataldo)c403445
Fix: warn constant on RHS of || in no-constant-condition (fixes #11181) (#11253) (Merlin Mason)9194f45
Fix: Manage severity of 1 with TAP reporter (fixes #11110) (#11221) (Gabriel Cousin)000f495
Docs: fix example for sort-imports ignoreDeclarationSort (#11242) (Remco Haszing)7c0bf2c
Docs: Addnpx
usage to Getting Started guide (#11249) (eyal0803)da9174e
Docs: fixes typo peerDepencies (#11252) (Christian Kühl)9c31625
Docs: Improve custom formatter docs (#11258) (Nicholas C. Zakas)Commits
The new version differs by 12 commits.
faf3c4e
5.12.1
1010c98
Build: changelog update for 5.12.1
eb5c401
Chore: use meta.messages in some rules (2/4) (refs #9870) (#10773)
aa56247
Fix: avoid loading core rules dynamically from FS in Linter (#11278)
04450bb
Docs: clarify process for adding committers (#11272)
3ffcf26
Docs: add @g-plane as committer (#11277)
c403445
Fix: warn constant on RHS of || in no-constant-condition (fixes #11181) (#11253)
9194f45
Fix: Manage severity of 1 with TAP reporter (fixes #11110) (#11221)
000f495
Docs: fix example for sort-imports ignoreDeclarationSort (#11242)
7c0bf2c
Docs: Add
npx
usage to Getting Started guide (#11249)da9174e
Docs: fixes typo peerDepencies (#11252)
9c31625
Docs: Improve custom formatter docs (#11258)
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: