Repository navigation
Releases
piace 0.7.0
Statically linked, CGO-free binaries for linux/amd64, linux/arm64,
darwin/amd64 and darwin/arm64.
Verifying this download
Verify the signature first. The checksum manifest shows only that a
download is intact; the signature over it is what says where it came
from, and it is produced by the publishing workflow itself, so it is
attached from the moment this release exists.
cosign verify-blob SHA256SUMS \
--bundle SHA256SUMS.sigstore.json \
--certificate-identity 'https://github.com/example42/piace/.github/workflows/ci.yml@refs/tags/v0.7.0' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
sha256sum --check --ignore-missing SHA256SUMS # shasum -a 256 on macOS
./piace-0.7.0-<os>-<arch> versionThe binaries also carry a GitHub build provenance attestation naming the
workflow and commit that produced them:
gh attestation verify piace-0.7.0-linux-amd64 --repo example42/piaceSHA256SUMS.asc, a detached OpenPGP signature over the same manifest,
is attached separately for sites that require one. It is an extra, not the
verification path: see docs/release.md.
SHA256SUMS
2b3b8ebcf1dcb3185710e8fe1e6b25dd2e7dadc192cda29031c2f80daaf01ed6 piace-0.7.0-darwin-amd64
de66bca22fcb1147c8cf3a8ed391e3204d49b557fd8e346068337e005d7ee4bb piace-0.7.0-darwin-arm64
6700ac13fa3cedfc6fe31710d78e0b9f56fcb2637d46ec78dbae720ce3bb66ef piace-0.7.0-linux-amd64
9d749246cfc51a9484a4485199ae0a840f8a31c3ab22b87f3f5773c45a18a050 piace-0.7.0-linux-arm64
piace 0.6.0
Statically linked, CGO-free binaries for linux/amd64, linux/arm64,
darwin/amd64 and darwin/arm64.
Verifying this download
Verify the signature first. The checksum manifest shows only that a
download is intact; the signature over it is what says where it came
from, and it is produced by the publishing workflow itself, so it is
attached from the moment this release exists.
cosign verify-blob SHA256SUMS \
--bundle SHA256SUMS.sigstore.json \
--certificate-identity 'https://github.com/example42/piace/.github/workflows/ci.yml@refs/tags/v0.6.0' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
sha256sum --check --ignore-missing SHA256SUMS # shasum -a 256 on macOS
./piace-0.6.0-<os>-<arch> versionThe binaries also carry a GitHub build provenance attestation naming the
workflow and commit that produced them:
gh attestation verify piace-0.6.0-linux-amd64 --repo example42/piaceSHA256SUMS.asc, a detached OpenPGP signature over the same manifest,
is attached separately for sites that require one. It is an extra, not the
verification path: see docs/release.md.
SHA256SUMS
055f7083b8c8efabbe51f4bdfdf9806c6b90ae458104ca920ec2094f594ecb92 piace-0.6.0-darwin-amd64
c22dd205c7e7a4a22d46e05c646f28b178fc40044824cdd0a74ff901c5d711b1 piace-0.6.0-darwin-arm64
720d3220fde1781a2f1a82053af2f3e8983817a508db323994929e6c5a4fe3f1 piace-0.6.0-linux-amd64
b0b1d5196ba842d4efc3e21f24d89c13a5277273770878ab5a1080ed279329aa piace-0.6.0-linux-arm64
piace 0.5.0
Statically linked, CGO-free binaries for linux/amd64, linux/arm64,
darwin/amd64 and darwin/arm64.
Verifying this download
Verify the signature first. The checksum manifest shows only that a
download is intact; the signature over it is what says where it came
from, and it is produced by the publishing workflow itself, so it is
attached from the moment this release exists.
cosign verify-blob SHA256SUMS \
--bundle SHA256SUMS.sigstore.json \
--certificate-identity 'https://github.com/example42/piace/.github/workflows/ci.yml@refs/tags/v0.5.0' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
sha256sum --check --ignore-missing SHA256SUMS # shasum -a 256 on macOS
./piace-0.5.0-<os>-<arch> versionThe binaries also carry a GitHub build provenance attestation naming the
workflow and commit that produced them:
gh attestation verify piace-0.5.0-linux-amd64 --repo example42/piaceSHA256SUMS.asc, a detached OpenPGP signature over the same manifest,
is attached separately for sites that require one. It is an extra, not the
verification path: see docs/release.md.
SHA256SUMS
67bd0834f110b8edb701677a8125194809b669ad6bec9b9909a1bd3e71e11f50 piace-0.5.0-darwin-amd64
19f2a375f376e849c5c68d422b602fcb4c8c839eeb6e9a3e81b048de839bc716 piace-0.5.0-darwin-arm64
cb960d1b7117b5928a5f8ccfd6324c698214b76a586b3d8ded497d2d481ac468 piace-0.5.0-linux-amd64
fbe1124c477c1d923c1a058a618d0020edcc8109a1dba8173c17fbb8cfce0faa piace-0.5.0-linux-arm64
piace 0.4.0
Statically linked, CGO-free binaries for linux/amd64, linux/arm64,
darwin/amd64 and darwin/arm64.
Verifying this download
Verify the signature first. The checksum manifest shows only that a
download is intact; the signature over it is what says where it came
from, and it is produced by the publishing workflow itself, so it is
attached from the moment this release exists.
cosign verify-blob SHA256SUMS \
--bundle SHA256SUMS.sigstore.json \
--certificate-identity 'https://github.com/example42/piace/.github/workflows/ci.yml@refs/tags/v0.4.0' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
sha256sum --check --ignore-missing SHA256SUMS # shasum -a 256 on macOS
./piace-0.4.0-<os>-<arch> versionThe binaries also carry a GitHub build provenance attestation naming the
workflow and commit that produced them:
gh attestation verify piace-0.4.0-linux-amd64 --repo example42/piaceSHA256SUMS.asc, a detached OpenPGP signature over the same manifest,
is attached separately for sites that require one. It is an extra, not the
verification path: see docs/release.md.
SHA256SUMS
5c564f8a87b6405110e7c8f2ec2864100cd0ae5e1261cd5559a0ed65636a664f piace-0.4.0-darwin-amd64
856b40dcb5e94a34fc7bde6cbd4a8fa222e665fb41c31ff2e3ee1065362983fb piace-0.4.0-darwin-arm64
6cb0cd87f5913dbba2f01e3aefa4605dee31b33b602ea2b51ed50f4df77d9149 piace-0.4.0-linux-amd64
df9dc4ff9c79ebebdc8ed67c3291705b50014cdf402d3d27a004c740d5fee263 piace-0.4.0-linux-arm64
piace 0.3.0
Statically linked, CGO-free binaries for linux/amd64, linux/arm64,
darwin/amd64 and darwin/arm64.
Verifying this download
Verify the signature first. The checksum manifest shows only that a
download is intact; the signature over it is what says where it came
from, and it is produced by the publishing workflow itself, so it is
attached from the moment this release exists.
cosign verify-blob SHA256SUMS \
--bundle SHA256SUMS.sigstore.json \
--certificate-identity 'https://github.com/example42/piace/.github/workflows/ci.yml@refs/tags/v0.3.0' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
sha256sum --check --ignore-missing SHA256SUMS # shasum -a 256 on macOS
./piace-0.3.0-<os>-<arch> versionThe binaries also carry a GitHub build provenance attestation naming the
workflow and commit that produced them:
gh attestation verify piace-0.3.0-linux-amd64 --repo example42/piaceSHA256SUMS.asc, a detached OpenPGP signature over the same manifest,
is attached separately for sites that require one. It is an extra, not the
verification path: see docs/release.md.
SHA256SUMS
69da4370659c1034e85044850e2bb268b5bf939cb074c4166f4440b9fa0df8e6 piace-0.3.0-darwin-amd64
bd588ffe5f2fa799edd75ece1e8eeafe17051631341f4717ec1339b2cce1b080 piace-0.3.0-darwin-arm64
62046eb71d77681ef226cbee30a6f8ee68f9281b06dc9335609b47007cc4e985 piace-0.3.0-linux-amd64
d17d1b58678a525c0b3a005903ee167ac60700a5a02dc21e4cf8d424ee2b66c6 piace-0.3.0-linux-arm64
piace 0.2.1
Statically linked, CGO-free binaries for linux/amd64, linux/arm64,
darwin/amd64 and darwin/arm64.
Verifying this download
sha256sum --check --ignore-missing SHA256SUMS # shasum -a 256 on macOS
./piace-0.2.1-<os>-<arch> versionSHA256SUMS.asc — the detached OpenPGP signature over the manifest — is
signed and attached separately after publication; this workflow holds no
signing key. Until it appears, the checksums above show only that a download
is intact, not where it came from. See docs/release.md for the full
procedure and the signing key fingerprint.
SHA256SUMS
7cba7e3867302bd9ef92d4dc140977546fd0ad9b8ad4e8da203154b316e54e50 piace-0.2.1-darwin-amd64
1a688d213306e9003c6117d7246bbd20e36de3eb1ee393a881d2846bcd8b129f piace-0.2.1-darwin-arm64
fbc754a36840059c43415d633bee3014121773db9c8663fd8193cbbef79cedbd piace-0.2.1-linux-amd64
d1ee761edcd9f1c432399a055319d122ade7bfdc7b5293788737b3bf2a8d795a piace-0.2.1-linux-arm64
piace 0.2.0
Statically linked, CGO-free binaries for linux/amd64, linux/arm64,
darwin/amd64 and darwin/arm64.
Verifying this download
sha256sum --check --ignore-missing SHA256SUMS # shasum -a 256 on macOS
./piace-0.2.0-<os>-<arch> versionSHA256SUMS.asc — the detached OpenPGP signature over the manifest — is
signed and attached separately after publication; this workflow holds no
signing key. Until it appears, the checksums above show only that a download
is intact, not where it came from. See docs/release.md for the full
procedure and the signing key fingerprint.
SHA256SUMS
5f95789f714e0e839e6f1bbef4c19cf4eec0a89b0308249b2932780a0b6476d1 piace-0.2.0-darwin-amd64
74f7bf51e1923c1f71d83f989662eb0de411f1ba15b46f2562222ad9c520fa2f piace-0.2.0-darwin-arm64
b6ae6261e786584530526a75d9d3c62fef086fc499320af38d61407a63591eb9 piace-0.2.0-linux-amd64
c6f81d1bb66117dbc98b1174bbd9639763d43e39745ded7ed3b82330bd2db5bd piace-0.2.0-linux-arm64
piace 0.1.0
Statically linked, CGO-free binaries for linux/amd64, linux/arm64,
darwin/amd64 and darwin/arm64.
Verifying this download
sha256sum --check --ignore-missing SHA256SUMS # shasum -a 256 on macOS
./piace-0.1.0-<os>-<arch> versionSHA256SUMS.asc — the detached OpenPGP signature over the manifest — is
signed and attached separately after publication; this workflow holds no
signing key. Until it appears, the checksums above show only that a download
is intact, not where it came from. See docs/release.md for the full
procedure and the signing key fingerprint.
SHA256SUMS
99acd0a10d4d77ed8c955fbc3b594097aa58f52897d0d692d6c1dfccb613dcd7 piace-0.1.0-darwin-amd64
f059f05e901602b426c2d029ae6833d890051e0a5e6b740b82203c871aab54c3 piace-0.1.0-darwin-arm64
776735131a4d024c462149becec9d1ee39d30d021c2eead3edfbdd390746a1ab piace-0.1.0-linux-amd64
a923b3bf74141bd338d2f6a9fa619a7ae85ea5313b684a20cbfcf6ea1f9a0f32 piace-0.1.0-linux-arm64