Tables for parsing PowerShell commands landed, groundwork for judging Windows command safety.
What's wrong with this entry?
Constants for taking PowerShell commands apart land in the build: the common parameters -erroraction, -warningaction, -informationaction, -progressaction with aliases -ea, -wa, -infa, -proga; variable-capturing parameters such as -errorvariable, -outvariable, -pipelinevariable; scope names, action values including the numeric forms, an approved-verb list, a Unicode whitespace splitter and a smart-quote pattern.
- Consistent with tighter safety analysis of PowerShell commands; the code consuming these tables is elsewhere in the bundle.
-responseheadersvariable
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.
-
v2.1.234
Windows policy helpers can be PowerShell scripts
Both mention window
-
v2.1.234
Windows sandbox refusals now say why an exclusion did not apply
Both mention window
-
v2.1.234
Terminal is restored on Ctrl+Break on Windows
Both mention window