fix(wfctl): preserve registry download checksums#853
Conversation
There was a problem hiding this comment.
Pull request overview
This PR enhances wfctl plugin registry-sync to optionally read checksums.txt from GitHub releases and, when available, include sha256 values in generated downloads entries in registry manifests—improving downstream install integrity verification while remaining compatible with plugins that don’t publish checksums.
Changes:
- Extend release asset metadata to include an optional
sha256field and plumb it into manifestdownloadsentries during--fix. - Add support code to download and parse
checksums.txtfrom a release (best-effort / optional). - Add unit tests for parsing release checksums and for emitting
sha256inapplyFixoutput.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| cmd/wfctl/plugin_registry_sync.go | Adds sha256 support to release downloads and introduces checksums.txt download + parsing for registry-sync. |
| cmd/wfctl/plugin_registry_sync_test.go | Adds tests covering checksums parsing and ensuring applyFix writes sha256 when provided. |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
⏱ Benchmark Results✅ No significant performance regressions detected. benchstat comparison (baseline → PR)
|
Summary
Verification