Skip to content

Align README with published v1.0.11 raw asset #4

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
chen21019 merged 1 commit into from
Sep 12, 2026
Merged

Align README with published v1.0.11 raw asset #4

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
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,17 +47,17 @@ Build on Linux:
Package the primary artifact and compatibility alias:

```sh
VERSION_OVERRIDE=v1.0.10 SOURCE_DATE_EPOCH=0 ARCH=amd64 ./scripts/package
VERSION_OVERRIDE=v1.0.11 SOURCE_DATE_EPOCH=0 ARCH=amd64 ./scripts/package
```

The `release.yml` workflow checks the next `v1.0.11` raw Linux amd64 binary on
The `release.yml` workflow checks the `v1.0.11` raw Linux amd64 binary on
pull requests and `main`: Go 1.27.0 build identity, race tests, vet, source and
binary vulnerability/secret scans, a CycloneDX SBOM, and SHA-256 checksums.
It publishes nothing automatically. A maintainer may dispatch it from `main`
after the checks pass; the workflow then creates an annotated numeric tag and
attaches the verified raw binary, archive, SBOM, scan evidence, and checksums
to the GitHub Release. The v1.0.10 command above remains the currently
published package example until that release completes.
to the GitHub Release. The published `v1.0.11` release includes the raw binary
and `SHA256SUMS`; verify the downloaded file before deploying it.

## Unprivileged Tests

Expand Down