You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Signing: minisign over a checksums file is the primary signature, because it can be checked with one public key and no network. GitHub artifact attestations (sigstore) come on top, for provenance.
SBOM: CycloneDX JSON (cargo-cyclonedx). SPDX only if someone asks for it.
.github/workflows/release.yml: on a v* tag it checks the tag against the Cargo.toml version and builds comline for five targets (x86_64-unknown-linux-musl and aarch64-unknown-linux-musl, static and smoke-tested on Debian 9 and busybox; aarch64-apple-darwin, x86_64-apple-darwin; x86_64-pc-windows-msvc).
Each build is packaged as comline-<target>.tar.gz (.zip on Windows), with a SHA256SUMS.
Each archive is attested with GitHub build provenance.
A draft GitHub Release is created for a person to publish.
Cargo.toml has [package.metadata.binstall], so cargo binstall --git https://github.com/ComlineProject/cli comline finds the archives. A glibc host falls back to the musl archive.
Left to do
Signing with minisign, as decided above: one signature over SHA256SUMS, plus per-archive .sig files if binstall's signature check needs them.
The user generates the key pair. The secret key and its password go in as MINISIGN_SECRET_KEY and MINISIGN_PASSWORD, scoped to a release environment.
The public key goes in [package.metadata.binstall.signing], the README and RELEASING.md.
The release job checks the signatures against that public key and fails if they don't match. It never releases unsigned.
PR CI tests signing and verification with a throwaway key, including a tampered archive that must fail.
RELEASING.md describes key rotation and how to verify a download by hand.
SBOM: CycloneDX JSON from cargo-cyclonedx, attached to the release, and signed and checksummed with the archives.
Reproducible builds: rebuild from source and compare the bytes.
First real tag (v0.2.0 or later) exercises the Attest and Draft release jobs, which PR CI skips. Afterwards, check cargo binstall --git … comline against the published release on each OS.
Docker Hub pulls: the smoke job pulls debian:9 and busybox from Docker Hub, which can hit rate limits. Mirror them to GHCR if that happens.
Signing: minisign over a checksums file is the primary signature, because it can be checked with one public key and no network. GitHub artifact attestations (sigstore) come on top, for provenance.
SBOM: CycloneDX JSON (cargo-cyclonedx). SPDX only if someone asks for it.
Progress (2026-11-15).#159 added .github/workflows/release.yml. On a v* tag it does the following:
checks that the tag matches the Cargo.toml version;
builds comline for five targets:
x86_64-unknown-linux-musl and aarch64-unknown-linux-musl, static, built in the ci-tools image. They are smoke-tested on Debian 9 (glibc 2.24) and on busybox (uclibc).
aarch64-apple-darwin and x86_64-apple-darwin;
x86_64-pc-windows-msvc;
packages each build as comline-<target>.tar.gz, or .zip on Windows;
writes a SHA256SUMS;
attests each archive with GitHub build provenance;
creates a draft GitHub Release for a person to publish.
Cargo.toml has [package.metadata.binstall], so cargo binstall --git https://github.com/ComlineProject/cli comline will find the archives. A glibc host falls back to the musl archive.
Left to do
Signing with minisign, as decided above: one signature over SHA256SUMS, plus per-archive .sig files if binstall's signature check needs them.
The user generates the key pair. The secret key and its password go in as MINISIGN_SECRET_KEY and MINISIGN_PASSWORD, scoped to a release environment.
The public key goes in [package.metadata.binstall.signing], the README and RELEASING.md.
The release job checks the signatures against that public key and fails if they don't match. It never releases unsigned.
PR CI tests signing and verification with a throwaway key, including a tampered archive that must fail.
RELEASING.md describes key rotation and how to verify a download by hand.
SBOM: CycloneDX JSON from cargo-cyclonedx, attached to the release, and signed and checksummed with the archives.
Reproducible builds: rebuild from source and compare the bytes.
First real tag (v0.2.0 or later) exercises the Attest and Draft release jobs, which PR CI skips. Afterwards, check cargo binstall --git … comline against the published release on each OS.
Docker Hub pulls: the smoke job pulls debian:9 and busybox from Docker Hub, which can hit rate limits. Mirror them to GHCR if that happens.
Rewrote the body: the old text said the only install path is cargo install --path ., which has not been true since #159 (release workflow, static musl builds, SHA256SUMS, build-provenance attestations, binstall metadata). The body now carries the decisions, what #159 did (ticked) and the remaining checklist from the 2026-11-15 progress comment (minisign, SBOM, reproducible builds, first real tag, Docker Hub mirror, crates.io binstall). Original is in the edit history.
Activity
Kinflou commentedon Nov 9, 2026
Decided (docs#163):
cargo-cyclonedx). SPDX only if someone asks for it.Kinflou commentedon Nov 14, 2026
Progress (2026-11-15). #159 added
.github/workflows/release.yml. On av*tag it does the following:Cargo.tomlversion;comlinefor five targets:x86_64-unknown-linux-muslandaarch64-unknown-linux-musl, static, built in theci-toolsimage. They are smoke-tested on Debian 9 (glibc 2.24) and on busybox (uclibc).aarch64-apple-darwinandx86_64-apple-darwin;x86_64-pc-windows-msvc;comline-<target>.tar.gz, or.zipon Windows;SHA256SUMS;Cargo.tomlhas[package.metadata.binstall], socargo binstall --git https://github.com/ComlineProject/cli comlinewill find the archives. A glibc host falls back to the musl archive.Left to do
SHA256SUMS, plus per-archive.sigfiles if binstall's signature check needs them.MINISIGN_SECRET_KEYandMINISIGN_PASSWORD, scoped to areleaseenvironment.[package.metadata.binstall.signing], the README andRELEASING.md.RELEASING.mddescribes key rotation and how to verify a download by hand.cargo-cyclonedx, attached to the release, and signed and checksummed with the archives.v0.2.0or later) exercises the Attest and Draft release jobs, which PR CI skips. Afterwards, checkcargo binstall --git … comlineagainst the published release on each OS.debian:9andbusyboxfrom Docker Hub, which can hit rate limits. Mirror them to GHCR if that happens.cargo binstall comlinewithout--git) waits on Publish comline to crates.io #1.Kinflou commentedon Nov 15, 2026
Rewrote the body: the old text said the only install path is
cargo install --path ., which has not been true since #159 (release workflow, static musl builds, SHA256SUMS, build-provenance attestations, binstall metadata). The body now carries the decisions, what #159 did (ticked) and the remaining checklist from the 2026-11-15 progress comment (minisign, SBOM, reproducible builds, first real tag, Docker Hub mirror, crates.io binstall). Original is in the edit history.