What changed: Paths of the form C:filename (drive-relative, without a backslash) are now flagged and require manual approval rather than being resolved silently.
Details
- Drive-relative paths resolve against a per-drive current directory (a Windows quirk), which cannot be statically validated at permission-check time.
- Approval message:
Path '<path>' is drive-relative (resolves against the per-drive current directory, which cannot be statically validated) and requires manual approval.
Evidence
Drive-relative path check (search for "is drive-relative (resolves against the per-drive current directory")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.