You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
WindowsArea: what it touches
New FeaturesKind: in v2.1.232,
New FeaturesSection of the release
What
On Windows, file edits and Bash commands whose path crosses a Cygwin or Git Bash symlink cookie are refused. Git Bash follows those cookies but Node does not, so the two disagree about where a write lands. File-permission checks return a decision that the permission classifier cannot auto-approve; Bash returns an ask prompt naming the blocked path. Non-Windows platforms are unaffected.
Details
Denial reason: Path traverses a Cygwin-emulated symlink (Git Bash follows it, Node does not) — manual approval required, with (destination: …) appended when the resolver can name a target.
The file-side check sets classifierApprovable: !1; the Bash side returns behavior: "ask" with the same reason plus a blockedPath.
A companion refusal covers cd-compound commands whose final working directory cannot be worked out without running them.
The whole resolver is new in this version; nothing equivalent shipped in v2.1.231.
Evidence
Path traverses a Cygwin-emulated symlink (Git Bash follows it, Node does not) \u2014 manual approval required
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
