{"version":"2.1.232","anchor":"windows-paths-that-go-through-a-cygwin-emulated-symlink-now-","canonical_anchor":"windows-paths-that-go-through-a-cygwin-emulated-symlink-now-","heading":"Windows: paths that go through a Cygwin-emulated symlink now require manual approval","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/windows-paths-that-go-through-a-cygwin-emulated-symlink-now-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Windows: paths that go through a Cygwin-emulated symlink now require manual approval\n\nOn Windows, edits and commands crossing a Git Bash symlink now need your manual approval.\n\n**What**\n\nOn 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.\n\n**Details**\n\n- Denial reason: `Path traverses a Cygwin-emulated symlink (Git Bash follows it, Node does not) \u2014 manual approval required`, with `(destination: \u2026)` appended when the resolver can name a target.\n- The file-side check sets `classifierApprovable: !1`; the Bash side returns `behavior: \"ask\"` with the same reason plus a `blockedPath`.\n- A companion refusal covers `cd`-compound commands whose final working directory cannot be worked out without running them.\n- The whole resolver is new in this version; nothing equivalent shipped in v2.1.231.\n\n**Evidence**\n\n`Path traverses a Cygwin-emulated symlink (Git Bash follows it, Node does not) \\u2014 manual approval required`\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}