{"version":"2.1.232","anchor":"trusting-a-folder-no-longer-trusts-it-via-a-directory-above-","canonical_anchor":"trusting-a-folder-no-longer-trusts-it-via-a-directory-above-","heading":"Trusting a folder no longer trusts it via a directory above the repository","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/trusting-a-folder-no-longer-trusts-it-via-a-directory-above-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Trusting a folder no longer trusts it via a directory above the repository\n\nTrusting your home folder no longer silently trusts every project beneath it.\n\n**What**\n\nDeciding whether you have already accepted the trust prompt for a directory used to search every parent folder up to the filesystem root, so trusting something like your home directory silently trusted everything beneath it. The search is now bounded to the enclosing repository root and returns \"not trusted\" as soon as it would step above it.\n\n**Details**\n\n- The bound is a prefix check against the resolved repository root, so an accepted ancestor outside that root is rejected.\n- The old `skipCanonicalKeyProbe` option is renamed `advisoryNoFsProbe` and still performs the unbounded walk, without touching the filesystem.\n\n**Evidence**\n\n`hasTrustDialogAccepted`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}