{"version":"2.1.247","anchor":"snapshot-restore-checks-file-mode-not-just-content","canonical_anchor":"snapshot-restore-checks-file-mode-not-just-content","heading":"Snapshot restore checks file mode, not just content","tier":"notice","area":"Snapshots","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/snapshot-restore-checks-file-mode-not-just-content","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Snapshot restore checks file mode, not just content\n\nSnapshot restore now catches file permission changes, so an executable bit flip isn't missed.\n\n**What**\n\nWhen a workspace snapshot holds files at their committed state, it now records each path's file mode alongside its content id and fails the snapshot if either differs from what the commit holds. An executable-bit change can no longer pass as an unchanged file.\n\n**Details**\n\n- The check reads git's staged file listing including mode, and the mismatch is reported with the existing wording `are not the ones HEAD holds`.\n- Not gated; runs as part of the normal snapshot path.\n\n**Evidence**\n\n`are not the ones HEAD holds`\n\n- Area: Snapshots\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}