Update lint-staged to the latest version 🚀 #108
Merged
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
Contributor
Author
Version 6.1.0 just got published. |
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.
Version 6.0.1 of lint-staged was just published.
The version 6.0.1 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of lint-staged.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v6.0.16.0.1 (2018-01-19)
Bug Fixes
Commits
The new version differs by 15 commits.
e48402erefactor: Do not pass redundant param for searchPath2d8981bchore(package): update lockfile80596c3fix(package): update cosmiconfig to version 4.0.08baab8cdocs: Update inconsistent docs for filtering files (#374)237d3f6chore(package): upgrade to jest 22 (#367)4cd6aefci(travis): Updatesemantic-releaseconfig (#371)8e3545ctest: Useexpect.assertions()to test async codes (#377)e39d1deci: Cache dependencies (#378)a845bb2chore(scripts): replacenpm runwithyarn(#370)aeb4dfbchore: commityarn.lock(#368)3340357chore(package): update prettier to version 1.9.2 (#359)29c3715chore(package): Update prettier to version 1.9.1 (#354)f0c4686chore(package): Update prettier to version 1.9.0 (#353)cf87b61docs(README): Add link to releases for changelog (#349)023ad73chore(github): Add issue template (#351)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 🌴