Update gulp-eslint to version 3.0.1 🚀 #9542
Merged
Conversation
This file contains 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
BerkeleyTrue
added
greenkeeper
status: waiting review
|
@BerkeleyTrue I've verified that this update doesn't brake anything. Are we going to merge this now or you'll do this in #7430? |
BerkeleyTrue
force-pushed
the
greenkeeper-gulp-eslint-3.0.1
branch
from
b6c8060
to
83e5341
Compare
|
@greenkeeperio-bot updated the pull request. |
|
@greenkeeperio-bot updated the pull request. |
BerkeleyTrue
force-pushed
the
greenkeeper-gulp-eslint-3.0.1
branch
from
83e5341
to
87e5596
Compare
|
@bugron Thanks for verifying. This can be merged. |
BerkeleyTrue
removed
the
status: waiting review
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,
gulp-eslint just published its new version 3.0.1.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of gulp-eslint.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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!
🌴
The new version differs by 26 commits .
6059c223.0.1b0c2816ensure sharable config works08b9212test the case where babel-eslint is actually usefuleb98701mock stream-mode vinyl files with from2-stringbcd7736fix invalidenvsoption286b0c4remove unused fixturese2723e1Remove unnecessaryobject-assigndependency82c19493.0.097d8638Remove invalid options in example code505779dRemove option aliases7228608Bump ESLint to v3.x and ES2015ify946e0e92.1.0a01671eAdd v2.1.0 release note87213fdFix inline config example in README (#159)4de3d64Test on the latest/LTS NodeThere are 26 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade