Build: verify koffi Windows binaries against the lockfile; release install steps #5
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/koffi-integrity-release"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Verify koffi's Windows binaries; release install steps
The build downloads koffi's Windows native prebuilds with
npm pack(npm only installs the host platform's) and previously checked only the version. It now hashes each downloaded tarball and requires it to match the sha512 integrity locked for that package inpackage-lock.json, failing closed if the entry is missing, at another version, or has no sha512 hash. The shipped native code is therefore exactly the locked version.INSTALL.md gains From a release: download the plugin and
SHA256SUMS.txtfrom the Forgejo release and check the file with PowerShellGet-FileHash.Tested: normal build (both hashes match), corrupted lock hash (build fails), multi-hash lock entry (passes on its sha512), sha1-only entry (fails). 115 unit tests, manifest validation.
Review-gate: gpt-6.1-sol ship (nits on multi-hash parsing and INSTALL wording applied)
🤖 Generated with Claude Code