fix(deps): update module github.com/bmatcuk/doublestar to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/bmatcuk/doublestar	v1.3.4 -> v4.7.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

bmatcuk/doublestar (github.com/bmatcuk/doublestar)

v4.7.1: Fixed FilepathGlob("")

Compare Source

To be consistent with filepath.Glob, FilepathGlob("") returns nil.

v4.7.0: Added MatchUnvalidated, PathMatchUnvalidated

Compare Source

These functions provide a small performance improvement in cases where you don't care about whether or not the pattern is valid (maybe because you already ran ValidatePattern).

v4.6.1: Fixed Match bug with patterns like `a/**/`

Compare Source

Thanks @​mmxmb for submitting the bug and opening a PR in #​89!

v4.6.0: Added WithNoFollow

Compare Source

Added a WithNoFollow option for Glob, GlobWalk, and FilepathGlob that will cause doublestar to not follow symlinks. However, note that there is a caveat due to io/fs limitations: if the pattern mentions a symlink before any meta characters, those symlinks will be followed. For example: path/to/symlink/* will follow the symlink, assuming it is valid and links to a directory. path/** and path/*/symlink/* will not follow the symlink.

v4.5.0: Added WithFilesOnly

Compare Source

Added a new option for Glob, GlobWalk, and FilepathGlob called WithFilesOnly that will cause these functions to only return files. For example, a pattern such as folder/* will only return the files inside the folder, and not any directories. Note that symlinks to directories are considered directories for this purpose.

v4.4.0: Added WithFailOnPatternNotExist

Compare Source

Added the option WithFailOnPatternNotExist to Glob, GlobWalk, and FilepathGlob. This option will cause doublestar to abort if the pattern references a path that does not exist, for example, nonexistent/path/*.

v4.3.2

Compare Source

v4.3.1: Fixed Glob Bug With Pattern That Has Nonexistent Path And WithFailOnIOErrors

Compare Source

If the WithFailOnIOErrors option was set and the pattern contained a reference to a nonexistent path (such as nonexistent/path/*), Glob would return ErrNotExist. It now returns an empty result with no error as expected.

For anyone that would prefer that doublestar returned an error, I'll be adding that as a feature (and a separate option) later.

v4.3.0: Added Support for GlobOptions

Compare Source

This release adds options to Glob, GlobWalk, and FilepathGlob. At the moment, the only option is WithFailOnIOErrors that will cause doublestar to fail and return an error if it encounters any IO errors. It can be used like:

doublestar.Glob(fsys, pattern, WithFailOnIOErrors())

Thanks @​fho!

v4.2.0: Added Support for SkipDir to GlobWalk

Compare Source

Your callback to GlobWalk can now return SkipDir which functions as it does in the standard library: if the current path is a directory, GlobWalk will not recurse into it. If the current path is not a directory, GlobWalk will stop processing the parent directory.

v4.1.0: Added FilepathGlob Convenience Func; Better Support for Escaped Meta Chars

Compare Source

FilepathGlob is a convenience function for people who want a drop-in replacement for filepath.Glob().

Thanks sebastien-rosset

v4.0.3: Fixed a bug with {alts} and /* backtracking

Compare Source

v4.0.2: Fixed a bug with escaped characters

Compare Source

Thanks @​micimize!

v4.0.1: Fixed Windows Bugs

Compare Source

Fixed some Windows bugs in v4.0.0.

v4.0.0: Complete Rewrite for Performance and io/fs Support

Compare Source

v4 is a complete rewrite with a focus on performance. Additionally, doublestar has been updated to use the new io/fs package for filesystem access. As a result, it is only supported by golang v1.16+. See README.md and UPGRADING.md for additional information.

v3.0.0: Negate Character Classes with Exclamation Marks or Carets

Compare Source

To match POSIX patterns, v3 of doublestar supports negating character classes with exclamation marks (ie, [!...]) in addition to carets ([^...]). This is a minor breaking change if any of your existing patterns happen to include an exclamation mark as the first character in a character class. To fix the issue, simply escape the exclamation mark (ie, [\!...]) or move it later in the character class (ie, `[...!...]').

v2.0.4: Fixed Minor Recursion Bug

Compare Source

Thanks @​pavelbazika!

v2.0.3: Reduced Allocations

Compare Source

This release reduces some of the allocations in Match and PathMatch, improving performance. I've also added benchmarks in the tests.

v2.0.2: Close Directories Immediately

Compare Source

A small change to close directories immediately, rather than deferring. Thanks @​luhring!

v2.0.1: Fixed bug clobbering results if Readdir fails

Compare Source

If Readdir failed, doublestar was returning nil instead of the accumulated results. Thanks for the bug report @​InfiniteTF!

v2.0.0: Further abstraction for OS interface

Compare Source

doublestar only needs Readdir and the Closer interface for the type returned by OS.Open(). By changing the return type to this basic interface, it's even easier to abstract the calls to the filesystem for testing. This is an API change, though, necessitating a major version bump. Updating should be fairly easy. See: https://github.com/bmatcuk/doublestar/blob/master/UPGRADING.md

Thanks for the suggestion @​c4milo!

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.