-
Notifications
You must be signed in to change notification settings - Fork 0
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 🚨 #3
Comments
After pinning to 3.12.2 your tests are passing again. Downgrade this dependency 📌. |
Version 3.14.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv3.14.1
CommitsThe new version differs by 33 commits .
There are 33 commits in total. See the full diff. |
Version 3.16.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv3.16.0
CommitsThe new version differs by 81 commits .
There are 81 commits in total. See the full diff. |
Version 3.16.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv3.16.1
CommitsThe new version differs by 89 commits .
There are 89 commits in total. See the full diff. |
Version 3.17.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv3.17.0
CommitsThe new version differs by 118 commits .
There are 118 commits in total. See the full diff. |
Version 3.18.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv3.18.0
CommitsThe new version differs by 151 commits .
There are 151 commits in total. See the full diff. |
Version 3.13.0 of eslint just got published.
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
Release Notes
v3.13.0no-unneeded-ternary
(#7540) (Teddy Katz)padded-blocks
never
case (fixes #7868) (#7878) (alberto)operator-linebreak
(#7702) (Teddy Katz)return
argument (fixes #7594) (#7595) (Dalton Santos)semi
false positive before regex/template literals (fixes #7782) (#7783) (Teddy Katz)prefer-destructuring
rule (fixes #6053) (#7741) (Alex LaFroscia)Commits
The new version differs by 43 commits .
8571ab8
3.13.0
d54e0c1
Build: package.json and changelog update for 3.13.0
cd4c025
Update: add fixer for no-extra-label (#7840)
aa75c92
Fix: Ensure prefer-const fixes destructuring assignments (fixes #7852) (#7859)
4008022
Chore: Refactor to use ES6 Classes (Part 3)(refs #7849) (#7865)
c9ba40a
Update: add fixer for
no-unneeded-ternary
(#7540)dd56d87
Update: add object-shorthand option for arrow functions (fixes #7564) (#7746)
fbafdc0
Docs:
padded-blocks
never
case (fixes #7868) (#7878)ca1f841
Fix: no-useless-return stack overflow on loops after throw (fixes #7855) (#7856)
d80d994
Update: add fixer for object-property-newline (fixes #7740) (#7808)
bf3ea3a
Fix: capitalized-comments: Ignore consec. comments if first is invalid (#7835)
616611a
Chore: Refactor to use ES6 Classes (Part 2)(refs #7849) (#7847)
856084b
Chore: Refactor to use ES6 Classes (Part 1)(refs #7849) (#7846)
bf45893
Docs: Clarify that we only support Stage 4 proposals (#7845)
0fc24f7
Fix: adapt new-paren rule so it handles TypeScript (fixes #7817) (#7820)
There are 43 commits in total. 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 🌴
The text was updated successfully, but these errors were encountered: