Update lint-staged to the latest version 馃殌 #24
Closed
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.
Version 4.2.0 of lint-staged just got published.
The version 4.2.0 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 lint-staged.
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.
Release Notes
v4.2.04.2.0 (2017-09-15)
Features
Commits
The new version differs by 8 commits.
30fa594
feat: Print friendlier error if config is missing (#281)
0077644
chore: Cleanup
package.json
(#250)7abe23f
ci: Disable email notifications from Travis CI
c9d0849
docs: Use emojis in the Readme
e976a3c
docs: Add screenshot with the animated gif (#276)
92e586b
docs: Reformat code blocks
9b0282a
docs: Use diff formatting for code
33da9b3
ci: Whitelist build branches to avoid duplicate builds (#269)
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 馃尨