Update micromatch to the latest version 🚀 #792
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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 3.0.1 just got published. |
Version 3.0.2 just got published. |
|
Since we just released 3.0 I was just checking around for micromatch-related issues on GitHub and thought I'd stop in to say thanks while I'm at it! If you experience any issues with 3.0 please stop by and let us know on the micromatch issues. thanks! |
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 3.0.0 of micromatch just got published.
The version 3.0.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 micromatch.
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.
Commits
The new version differs by 75 commits.
e91c2f6Merge pull request #76 from micromatch/dev914059frun verb to generate readmec3bc209add more unit tests0f65651lint8d217f5update benchmarksc013ef9fix grammarad97d84Merge branch 'master' into devcfeaa29docsbf2cc5afix url0b679dcMerge pull request #88 from DianeLooney/masterafd2312Fixed the build badged44afb5adds examplesc2e1e0bminor editsf2503bbmovecomposeto main filee894de1remove dead code, minor re-orgThere are 75 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 🌴