You'll notice
Useful3 Signal2
PowerShell commands that write into variables or preferences now ask you before running.
What's wrong with this entry?
Anonymous. No account, no email.
What
Permission checks now scan PowerShell arguments for flags that write into an output variable or set a *Preference value, so those commands go to approval instead of being auto-allowed.
Details
- Handles backtick line continuations, colon-form parameters and abbreviated names such as
-evand-ov. - Separate messages for a flag on the top-level command and one inside a nested command.
Evidence
Variable-writing or ActionPreference argument in nested '${l.name}' requires approval
Strings lifted out of the shipped bundle, so the claim above can be checked against them.