Repository navigation
chore(deps): update dependency wcmatch to v12 - #63
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/wcmatch-12.x
branch
2 times, most recently
from
November 20, 2026 13:58
a77bab1 to
aa736db
Compare
renovate
Bot
force-pushed
the
renovate/wcmatch-12.x
branch
from
November 20, 2026 13:59
aa736db to
8e3fcc1
Compare
This branch has not been deployed
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:
==10.2.1→==12.0.4Release Notes
facelessuser/wcmatch (wcmatch)
v12.0.4Compare Source
12.0.4
bracex3.2.4 for minor bug fix..and..prefixes whenroot_diris missing oris not a directory.
v12.0.3Compare Source
12.0.3
GLOBTILDEnot expanding~in an exclusion pattern whenMINUSNEGATEis enabled, e.g.-~/*.py.v12.0.2Compare Source
12.0.2
bracex3.2.3 for a minor slash handling fix.**added byMATCHBASE(or bypathlib'smatch) being stacked on top of a patternthat already starts with
**or***.globmatchandmatchwould match dot files and directories withoutDOTGLOB, e.g.**withMATCHBASEmatcheda/.hidden/file, andmatch('**/x')matcheda/.hidden/x, which isnot what
globandrglobreturn. Inglob,***withMATCHBASEandGLOBSTARLONGstopped traversingsymlinks as
***was treated as a plain name pattern.MATCHBASEorpathlib'smatchandrglobadd an implicit**, andGLOBSTARLONGandFOLLOWare enabled, the implicit
**acts as***. As with any consecutive globstars, when it collapses with a**thatstarts the pattern, the result must still traverse symlinks, e.g.
rglob('**/a.txt')traverses symlinks, just likerglob('***/a.txt'), andglob('**')withMATCHBASEdoes too.globalso no longer treats a patternwith a slash, like
**/**, as having no slash just because its consecutive globstars collapse to one, whichdisagreed with
globmatch.globmatchwithREALPATHrejecting a path thatglobreturns when a directory symlink can bematched by a non-globstar component, e.g.
**/*/**/*.cssmatchingassets/linked/app.csswherelinkedis asymlink. The matcher now considers other ways of splitting the path between the
**s and the rest of the pattern,rather than only the first one the regular expression picks.
v12.0.1Compare Source
12.0.1
bracex3.2.2 for bug fixes.nothing, e.g.
**/?(a)matchingb. This also affects the implicit globstar used byMATCHBASEandpathlib.match.globmatchwithREALPATHrejecting a symlinked file when it is matched by a trailing**(e.g.
**ordir/**), disagreeing withgloband Bash, which both return such files.**and***components withGLOBSTARLONG, regardless of their order.v12.0Compare Source
12.0
BREAK: Various fixes to
!(...)patterns to more closely align to Bash. 100% Bash behavior is impossible withregular expression, but behavior in many ways was improved, but there may be some surprising behavior changes.
EXTGLOB/EXTMATCHinverse group,!(...), inside another group ignoring the rest of itsalternative and the text that follows the group, e.g.
@(!(a)b)and@(x|!(a))bmatchedab. They now followthe same rule as inverse groups that are not in a group. Inside
+(...)and*(...)groups, the rest is theremainder of the alternative and the text after the loop. The rest of the alternative was ignored since 7.0.1,
and the text after the group since 2.2.1.
EXTGLOB/EXTMATCHinverse group,!(...), inside another inverse group not ending where thetext consumed by the outer group ends, e.g.
!(!(a)|b)matchedaaand!(a!(b))matchedaba. This alsocaused
translate()withCAPTUREto match differently than without it for these patterns. This was aregression in 7.0.1.
EXTGLOB/EXTMATCHinverse group,!(...), whose patterns can only match text up to some length,e.g.
!(foo),!(a|bc), or!(?(a)b), now matches any other text, whatever follows it, as it does in Bash.For instance,
!(foo)*.txtnow matchesfoo.txtandfoobar.txt,!(a)*matchesa, and+(!(foo))matchesfoo. Inverse groups with patterns that can match text of any length, e.g.!(*.js), still need to know whatfollows them and behave as before. Inverse groups inside other inverse groups follow the same rules, e.g.
!(!(a)|b)*matchesaandab,!(!(a)*)matches nothing, and!(a!(b)*)no longer matchesab.EXTGLOB/EXTMATCHinverse group,!(...), whose patterns cannot match nothing can now matchnothing whenever the rest of the pattern matches, as it does in Bash, even when its patterns can match text of
any length. For instance,
!(*.js)*and!(a*)*now match any name (following dot rules), where!(*.js)*rejecteda.jsanda.json.BREAK: Match Bash logic such that
@(*|.a).bcan match.bin an extended pattern if the pattern contains anexplicit leading
.in one of the alternatives exists. In this scenario,*is allowed to match nothing before.b, but*won't physically match the..NEW: Generate tighter regular expressions with the same behavior.
FIX: A leading
*can no longer match nothing so that a literal dot can match the leading dot of a file name,e.g.
*.envno longer matches.envunlessDOTGLOB/DOTMATCHis enabled. This agrees with Bash, Python'sglob, andfnmatch, which already behaved this way. Use.*envto explicitly match hidden names.FIX: Fix
globandiglobmissing a file name without a directory part, e.g.a.txt, whendir_fdis filedescriptor
0, which a directory can get when it is opened while standard input is closed.FIX: Fix
WcMatchreturning a file afterkillis called from a directory validation hook or its errorhandler.
FIX: Preserve bare drive roots such as
D:inWcMatchon Windows, so searches use that drive's currentdirectory instead of its root directory.
FIX: Fix a
?or bracket expression after a leading*matching the leading dot of a file name, e.g.*?amatching
.a.FIX: Fix a wildcard in an
EXTGLOB/EXTMATCHgroup, such as?(old-)@(*), matching the leading dot of a filename when the text before it, e.g. an optional group or the start of another group slot, matched nothing. Wildcards
in later iterations of a repeated group, e.g.
+(.?|*)and.a., are no longer wrongly restricted.FIX: Fix an
EXTGLOB/EXTMATCH@(...)or+(...)group that can match nothing, e.g.@(?(a)),+(*(a))or@(a|?(b)), letting a literal dot after it match the leading dot of a file name, e.g.@(?(a)).hiddenmatching.hidden. Such a group must match something, so it can no longer be skipped to reachthe dot, as in Bash, unless
DOTGLOB/DOTMATCHis enabled or an alternative starts with a dot.FIX: Fix a
?or bracket expression at the start of a repeatedEXTGLOBgroup matching a path separator inglobmatchand related functions, e.g.+(?)matchinga/b. This was a regression in 11.0.1.FIX: Fix an
EXTGLOB/EXTMATCHgroup that is simplified to a different group type, e.g.@(+(b))or@(!(b)), losing its meaning when it is then reduced into its parent group. Repeats and negations were dropped,e.g.
@(a|@(!(b)))matchedband notc, and!(@(+(a)))matchedaa. This was a regression in 11.0.FIX: Preserve byte file names when globbing with
dir_fd, including names requiring surrogate escaping.FIX: Use the same case-insensitive matching for literal and wildcard path components in
globandiglob,including Unicode case equivalences.
FIX: Preserve a terminal directory separator after
GLOBSTARpatterns inglobmatch,globfilter, andtranslated patterns. Patterns such as
**/anddir/**/no longer match regular files.FIX: Require the literal prefix of recursive
globandiglobpatterns such asfile/**to name a directory.FIX: Count duplicate exclusion expansions toward the shared pattern limit in compiled matchers and translation.
FIX: Treat an empty
root_dir(''orb'') as the current directory inglobandiglob, including whenthe directory is selected with
dir_fd.FIX: Fix
globandiglobreturning synthetic.and..matches withSCANDOTDIRwhen a directorycannot be opened for scanning.
FIX: Require
bracex3.2.1 which contains a number of brace related bug fixes.v11.2Compare Source
11.2
bracex3.2 for various bug fixes.numpyarrays (@Lushiyao5).
*are used for file name matching. Performance is only improved incases where variable length
EXTGLOBpatterns would not interfere with matching. Issue found by (@gistrec).globandiglob, and preserveunlimited expansion across multiple patterns with negative limits.
WcMatchinstead of 32.finite limits when exclusions consume the entire pattern budget.
EXTGLOB/EXTMATCHinverse group,!(...), is followedby an extended group that contains another extended group, e.g.
!(a)@(b|*(c)).EXTGLOB/EXTMATCHstar group,*(...), being matched as literal text when it directly followsanother
*, e.g.a**(b).globandiglobreturning the same path twice when two patterns find it and case is ignored, e.g.['A*', '*b']withIGNORECASEand a file namedAb. Files that only differ by case are no longer treated asduplicates when the file system is case sensitive.
.or...such as
?(a)*, and avoid returning.and..from these directory scans.rglobtreating a pattern that starts with**or***as if it started with*, e.g.**/a.txtwith
GLOBSTARmisseda.txtin the searched folder and returneda.txtfrom inside a symlinked folder.v11.1Compare Source
11.1
WindowsPathsubclass construction on Python 3.12+ (#238).GLOBSTARcaptures (#239).v11.0.1Compare Source
11.0.1
expected from Wildcard Match in regards to security, and provide general information to allow users to make good
decisions.
EXTGLOB/EXTMATCHwas enabled.v11.0Compare Source
11.0
EXTGLOB/EXTMATCHregular expression patterns when possible to reduce deeplynested patterns.
<0-9>) via newNUMRANGEflag.EXTGLOB/EXTMATCHwas enabled. Due to the new feature added that reduces extended glob group nesting, groups nolonger appear exactly as specified. Moving forward, capturing groups are not included by default. If you need the
old behavior, it can be enabled in a
translate()call via theCAPTUREflag. This flag will cause extended globreduction to be turned off and for capturing groups to be enabled.
EXTGLOB/EXTMATCHparsing once an unclosed extended glob pattern is encountered.SPLITnot accounting for POSIX character class.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.