Update test-exclude to version 4.0.0 🚀 - #90
Open
greenkeeperio-bot wants to merge 1 commit into
Open
greenkeeperio-bot wants to merge 1 commit into
greenkeeperio-bot wants to merge 1 commit into
Conversation
Current coverage is 94.79% (diff: 100%)@@ master #90 diff @@
==========================================
Files 9 9
Lines 192 192
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
Hits 182 182
Misses 10 10
Partials 0 0
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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,
test-exclude just published its new version 4.0.0.
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 test-exclude.
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 35 commits .
d07955bchore(release): 4.0.06cd0d70chore(package): update dependencies (#24)59e8bbffeat: add coverage to default excludes (#23)cf979c7chore(release): 3.3.0f8f99c6feat: allow include/exclude rules to be a string rather than array (#22)5205235chore(release): 3.2.2d0cfbc3fix: we no longer need to add node_modules/** rulee5f853achore(release): 3.2.143008d5fix: setting dotfiles to true introduced a bug related to matching files in root directory27b249cfix: fix bug matching files in root, introduced by dotfiles setting3d0bf78chore(release): 3.2.034f5cbafeat: adds .test..js exclude rule (#20)346fb19chore(release): 3.1.018f910bfeat: we now support dot folders (#19)f2c1598feat: we now support dot foldersThere are 35 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.