release-tools¶
Release CI image: colophon, on ci-base
Release v0.2.4, 2026-11-20. Built on ci-base. Source: phpboyscout/images/release-tools.
Pin it¶
Pin the full version. Each release also moves its minor tag and latest, which change under you.
| Variant | Tags |
|---|---|
| default | v0.2.4, v0.2 |
About this image¶
The release track's CI image.
Contains colophon, on top of
ci-base.
One tool, and forge-neutral¶
colophon is the release orchestrator this estate owns. It proposes a release, confirms what actually landed on the target branch, and cuts the tag from that commit and nothing else.
It releases Go projects today and will release Rust, Node and static-site
projects too. That is why it is not in go-tools: a Rust repository should not
pull a Go toolchain, an ONNX Runtime shared library and goreleaser in order to
cut a tag.
Why not ci-base¶
The binary is 75 MB, and ci-base is the base every toolchain image derives
from — so putting colophon there would add it to node-tools, rust-tools,
tofu-tools and docs-tools, none of which will ever run it.
ci-base's charter is "bash, git, curl, jq, python3, ca-certificates. Nothing
else", and it reads that way because discord-release was pulling 2.36 GB to
run curl and jq. Adding 75 MB to five images to save one is the same mistake
with a smaller number.
What it needs at runtime¶
git, and network access to a forge. colophon does its own git work in-process
through go-git — it clones the target branch into memory rather than shelling
out — so the git binary is here for the runner's own checkout rather than for
colophon. No toolchain, no language runtime.
Verification¶
colophon comes from the release store at pkg.phpboyscout.uk, which is
mutable, so a tarball checked only against a checksums file from the same store
proves nothing. The build checks colophon's OpenPGP signature over
checksums.txt first, with gpgv, in a throwaway stage. The signature is made
by an AWS KMS key. Neither gpgv nor the key reaches the image.
The key is committed in keys/, and its fingerprint is pinned in the
COLOPHON_KEY build argument. The build fails unless the signature is valid and
made by that fingerprint.
To add or rotate the key, take it from https://keys.phpboyscout.uk/, confirm
its fingerprint against the one colophon pins in
internal/trustkeys/trustkeys_test.go on main, and move the key file and
COLOPHON_KEY in one commit. A revoked key keeps verifying until that commit
lands: gpgv sees no revocation. See
cicd spec 0120.
Consumed by¶
The colophon component in
phpboyscout/cicd — see cicd spec 0077.
Everything installed¶
Contents not yet published. This image's releases do not carry an SBOM yet. Until they do, the README above describes what it adds, and the Dockerfile is the full record.