Say the recorded digest is not a file checksum

sha256() refuses binary input, so the archive is hashed in its base64 form. Comparing it against sha256sum reads as corruption.
2026-09-12 00:23:08 +10:00
parent 3c73a83602
commit 3716131e56
2 changed files with 8 additions and 0 deletions
@@ -142,6 +142,10 @@ hrsh7th/cmp-path                 @main          start tracking branch main, fetc
 nvim-lua/plenary.nvim            v0.1.4         start installed
 ```

+The digest is a content identity, not a file checksum: Neovim's `sha256()`
+refuses binary input, so it hashes the archive's base64 form. It will not match
+`sha256sum <archive>`.
+
 A branch plugin is never reported as up to date: nothing on disk can know
 whether upstream has moved. After an update, an unchanged digest is reported as
 `unchanged` rather than as an update that changed nothing.
@@ -108,6 +108,10 @@ one. |:ArtiPackList| reports that rather than guessing: >
    hrsh7th/cmp-path     @main    start  tracking branch main, fetched
                                         2026-09-08 10:14 (7db8f64a)
 <
+The digest is a content identity, not a file checksum: Neovim's sha256()
+refuses binary input, so it hashes the archive's base64 form. It will not
+match sha256sum on the archive.
+
 A branch plugin is never reported as up to date, because nothing on disk can
 know whether upstream has moved. An update that brings back the same digest is
 reported as unchanged, not as an update.