{"version":"2.1.232","anchor":"powershell-commands-that-write-variables-now-ask-for-approva","canonical_anchor":"powershell-commands-that-write-variables-now-ask-for-approva","heading":"PowerShell commands that write variables now ask for approval","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/powershell-commands-that-write-variables-now-ask-for-approva","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### PowerShell commands that write variables now ask for approval\n\nPowerShell commands that write into variables or preferences now ask you before running.\n\n**What**\n\nPermission 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.\n\n**Details**\n\n- Handles backtick line continuations, colon-form parameters and abbreviated names such as `-ev` and `-ov`.\n- Separate messages for a flag on the top-level command and one inside a nested command.\n\n**Evidence**\n\n`Variable-writing or ActionPreference argument in nested '${l.name}' requires approval`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}