Complex bash double-bracket tests now bail out early instead of being misjudged by the permission scanner.
What's wrong with this entry?
The double-bracket regex scanner stops as soon as the parser desyncs rather than continuing and checking only the final depth.
- If paren depth ever goes negative mid-scan, the scanner returns a
too-complexresult withdifferential: !0.
[[ ]] regex has unbalanced parentheses (parser desync)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.