Update module github.com/bmatcuk/doublestar to v4#758
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/github.com-bmatcuk-doublestar-4.x
branch
from
fd1678d to
6c463d7
Compare
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
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.
This PR contains the following updates:
v1.3.4→v4.10.0Release Notes
bmatcuk/doublestar (github.com/bmatcuk/doublestar)
v4.10.0: Added WithNoHidden optionCompare Source
Added support for a
WithNoHiddenoption to ignore hidden files in patterns that might unintentionally match them. For example, a.configdirectory would not be matched by*or recursed into by**, but would be matched by.*or recursed by.config/**.Thanks to @lukasngl for the initial PR and idea!
What's Changed
New Contributors
Full Changelog: bmatcuk/doublestar@v4.9.2...v4.10.0
v4.9.2: Fixed Handling of Paths With Meta Chars Using AltsCompare Source
@toga4 submitted a PR that fixed a small bug with the way paths were handled when the pattern used
{alts}: if some part of the on-disk path that came before the{alt}included meta characters (say, a directory name that included the character?), these meta characters were not escaped when they were passed back through the globbing routines. This caused doublestar to interpret them as actual meta characters, rather than a fixed-string path as it should have. Nice find, @toga4 !What's Changed
New Contributors
Full Changelog: bmatcuk/doublestar@v4.9.1...v4.9.2
v4.9.1: Small Performance ChangeCompare Source
This release contains a small change that gives a slight performance increase. Thanks to @jbedard for the PR!
What's Changed
New Contributors
Full Changelog: bmatcuk/doublestar@v4.9.0...v4.9.1
v4.9.0: Added WithCaseInsensitive optionCompare Source
Added a
WithCaseInsensitiveoption to ignore alphabetic case when globbing. Thanks @braydonk for the PR!What's Changed
WithCaseInsensitiveGlobOptionby @braydonk in #106New Contributors
Full Changelog: bmatcuk/doublestar@v4.8.1...v4.9.0
v4.8.1: Small Performance Improvement for MatchUnvalidatedCompare Source
Skip some additional validation checks in
MatchUnvalidated. Thanks to @lukemassa for the PR!Additional documentation improvements from @timo-reymann. Thanks!
What's Changed
New Contributors
Full Changelog: bmatcuk/doublestar@v4.8.0...v4.8.1
v4.8.0: Fixed Escaped Meta in the "Base" of the PatternCompare Source
If the "base" of a pattern (ie, everything up to the first path slash before any meta characters) contains an escaped meta character, doublestar would fail to glob any files.
Thanks to @tdurieux for finding and fixing this bug!
Breaking-ish Change
I've updated
SplitPatternto unescape meta characters in the first returned string. I suspect this shouldn't cause issues for anyone because, if anyone was using this function, they've probably either never passed a pattern with escaped meta characters, or hand-rolled an unescape method to fix the bug - which will now be a no-op for them.What's Changed
New Contributors
Full Changelog: bmatcuk/doublestar@v4.7.1...v4.8.0
v4.7.1: Fixed FilepathGlob("")Compare Source
To be consistent with
filepath.Glob,FilepathGlob("")returns nil.v4.7.0: Added MatchUnvalidated, PathMatchUnvalidatedCompare 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 likea/**/Compare Source
Thanks @mmxmb for submitting the bug and opening a PR in #89!
v4.6.0: Added WithNoFollowCompare Source
Added a
WithNoFollowoption 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/**andpath/*/symlink/*will not follow the symlink.v4.5.0: Added WithFilesOnlyCompare Source
Added a new option for Glob, GlobWalk, and FilepathGlob called
WithFilesOnlythat will cause these functions to only return files. For example, a pattern such asfolder/*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 WithFailOnPatternNotExistCompare Source
Added the option
WithFailOnPatternNotExistto 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.2Compare Source
v4.3.1: Fixed Glob Bug With Pattern That Has Nonexistent Path And WithFailOnIOErrorsCompare Source
If the
WithFailOnIOErrorsoption was set and the pattern contained a reference to a nonexistent path (such asnonexistent/path/*), Glob would returnErrNotExist. 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 GlobOptionsCompare Source
This release adds options to
Glob,GlobWalk, andFilepathGlob. At the moment, the only option isWithFailOnIOErrorsthat will cause doublestar to fail and return an error if it encounters any IO errors. It can be used like:Thanks @fho!
v4.2.0: Added Support for SkipDir to GlobWalkCompare 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 CharsCompare 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 /* backtrackingCompare Source
v4.0.2: Fixed a bug with escaped charactersCompare Source
Thanks @micimize!
v4.0.1: Fixed Windows BugsCompare Source
Fixed some Windows bugs in v4.0.0.
v4.0.0: Complete Rewrite for Performance and io/fs SupportCompare 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 CaretsCompare 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 BugCompare Source
Thanks @pavelbazika!
v2.0.3: Reduced AllocationsCompare 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 ImmediatelyCompare Source
A small change to close directories immediately, rather than deferring. Thanks @luhring!
v2.0.1: Fixed bug clobbering results if Readdir failsCompare Source
If
Readdirfailed, doublestar was returningnilinstead of the accumulated results. Thanks for the bug report @InfiniteTF!v2.0.0: Further abstraction for OS interfaceCompare Source
doublestar only needs
Readdirand theCloserinterface for the type returned byOS.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.mdThanks for the suggestion @c4milo!
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.