Update fast-glob: 2.2.4 → 2.2.7 (patch)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ fast-glob (2.2.4 → 2.2.7) · Repo

Commits

See the full diff on Github. The new version differs by 28 commits:

• build(package): bump version to 2.2.7
• docs(readme): how to use UNC path
• fix(tasks): always mark patterns as dynamic with case-insensitive mode
• fix(providers): resolve path even for absolute filepath
• Add test for question mark glob
• Set is-glob strict to false
• Merge pull request #164 from mrmlnc/ISSUE-151_improve_documentation_about_entry_type
• Merge pull request #165 from mrmlnc/TRIVIAL_update_deps
• docs(README): clarify return type (fix #151)
• build: drop CI for Node.js 4
• build: fix build issue after update dependencies
• build: update @types/node
• style(index): use `T[]` instead of `Array<T>`
• Merge pull request #150 from mrmlnc/update_tslint_config
• build: update "tslint-config-mrmlnc" to 2.0.0
• Merge pull request #149 from mrmlnc/ISSUE-144_more_smoke_tests
• Merge pull request #148 from mrmlnc/ISSUE-144_fix_tests
• test(smoke): add test case for output with stats option
• refactor(adapters): don't use `Object.assign` for implicit class changes
• test(adapters): add test case for #144
• refactor: use fs.Stats class instead of object for tests
• chore(package): Bump version to 2.2.6
• Revert "build: update "tslint-config-mrmlnc" to 2.0.0"
• chore(package): Bump version to 2.2.5
• Merge pull request #142 from mrmlnc/update_tslint_config
• build: update "tslint-config-mrmlnc" to 2.0.0
• Merge pull request #141 from mrmlnc/FG-140_unhandled_stream_error
• fix: handle all error events

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)