{"version":"2.1.227","anchor":"file-sync-manifests-now-require-a-per-file-sha256","canonical_anchor":"file-sync-manifests-now-require-a-per-file-sha256","heading":"File-sync manifests now require a per-file sha256","tier":"internal","area":"File Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/file-sync-manifests-now-require-a-per-file-sha256","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### File-sync manifests now require a per-file sha256\n\nDirectory sync manifests must now include a sha256 for every file or they fail.\n\n**What**\n\nThe manifests used to sync a directory between machines must now include a 64-character hex sha256 digest for every file alongside path, size, mode and etag. Manifests without it fail validation.\n\n**Evidence**\n\n`sha256`\n\n- Area: File Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}