eslint@3.0.1 breaks build ⚠️ #55
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Changes Unknown when pulling 3c81c13 on greenkeeper-eslint-3.0.1 into * on master*. |
Scrum
force-pushed
the
greenkeeper-eslint-3.0.1
branch
from
3c81c13 to
2d836e5
Compare
Scrum
force-pushed
the
greenkeeper-eslint-3.0.1
branch
from
2d836e5 to
49bedec
Compare
Scrum
force-pushed
the
greenkeeper-eslint-3.0.1
branch
from
49bedec to
c330cd7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
eslint just published its new version 3.0.1.
This version is covered by your current version range and after updating it in your project the build kept failing.
It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
no-unused-varsfalse positive around callback (fixes #6576) (#6579) (Toru Nagashima)no-unused-varsignore for-in (fixes #2342) (#6126) (Oleg Gaidarenko)outerIIFEBodyinindent(fixes #6581) (#6584) (alberto)max-len(fixes #6564) (#6565) (not-an-aardvark)The new version differs by 14 commits .
0fd4b6d3.0.1ebf2987Build: package.json and changelog update for 3.0.127700cfFix:no-unused-varsfalse positive around callback (fixes #6576) (#6579)124d8a3Docs: Pull request template (#6568)e9a2ed9Docs: Fix rules\id-length exceptions typos (fixes #6397) (#6593)a2cfa1bFix: Make outerIIFEBody work correctly (fixes #6585) (#6596)9c451a2Docs: Use string severity in example (#6601)8308c0bChore: remove path-is-absolute in favor of the built-in (fixes #6598) (#6600)7a63717Docs: Add missing pull request step (fixes #6595) (#6597)de3ed84Fix: makeno-unused-varsignore for-in (fixes #2342) (#6126)6ef2cbeFix: strip Unicode BOM of config files (fixes #6556) (#6580)ee7fcfaDocs: Correct type ofouterIIFEBodyinindent(fixes #6581) (#6584)25fc7b7Fix: false negative ofmax-len(fixes #6564) (#6565)f6b8452Docs: Distinguish examples in rules under Stylistic Issues part 6 (#6567)See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade