On Windows, edits and commands crossing a Git Bash symlink now need your manual approval.
What's wrong with this entry?
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.
- 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 returnsbehavior: "ask"with the same reason plus ablockedPath. - 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.
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.
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