Skip to content

docs(readme): document SHA256SUMS release-verification flow (#66) #187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
quangdang46 merged 1 commit into from
May 22, 2026
+25 −0
Merged

docs(readme): document SHA256SUMS release-verification flow (#66) #187

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -720,6 +720,31 @@ brew tap 1jehuang/jcode
brew install jcode
```

### Verifying release artifacts

Each release publishes a single `SHA256SUMS` manifest covering every
Linux, macOS, and Windows asset attached to the release. Verify a
download before installing:

```bash
VERSION=v0.12.0
ARTIFACT=jcode-linux-x86_64.tar.gz # or jcode-macos-aarch64.tar.gz, jcode-windows-x86_64.tar.gz, etc.

curl -LO "https://github.com/quangdang46/jcode/releases/download/${VERSION}/${ARTIFACT}"
curl -LO "https://github.com/quangdang46/jcode/releases/download/${VERSION}/SHA256SUMS"
sha256sum --check --ignore-missing SHA256SUMS
```

Expected output:

```
jcode-linux-x86_64.tar.gz: OK
```

`SHA256SUMS` is generated in the release workflow from the actual
artifacts uploaded to the run, so it is always synchronized with the
binaries you can download.

### From Source (all platforms)

```bash
Expand Down