Update globby 14.1.0 → 15.0.0 (major)

[depfu]

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

What changed?

✳️ globby (14.1.0 → 15.0.0) · Repo

Release Notes

15.0.0

Breaking

• Require Node.js 20 4ae42c8

Fixes

• Fix expandDirectories not working with globstar patterns 98d691a
• Fix relative paths with gitignore option b4d78d8
• Fix gitignore patterns in subdirectories not applying recursively 2cb6088
• Fix TypeScript types for globbyStream to correctly yield strings 1c7f3ed

---

v14.1.0...v15.0.0

Does any of this look wrong? Please let us know.

Commits

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

• 15.0.0
• Require Node.js 20
• Fix `expandDirectories` not working with globstar patterns
• Fix relative paths with gitignore option
• Fix gitignore patterns in subdirectories not applying recursively
• Document performance implications of `gitignore` option
• Fix TypeScript types for `globbyStream` to correctly yield strings

---

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 recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

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

@​depfu cancel merge

Cancels automatic merging of this PR

@​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)

[RobinMalfait]

This now requires Node v20. All our GitHub Actions already use Node v20 so I think this should be fine.