Releases
How binaries are published from this repository.
Two channels, both static binaries for x86_64 and aarch64 with a checksum file next to each.
- Pre-releases. Every push to
mainbuilds on both architectures and publishes a pre-release named by the commit's short hash, with the commit message as its body. Images that want a specific build pin it. - Releases. A
MAJOR.MINOR.PATCHtag onmainbuilds and publishes a release. Its body isrelease-notes/<tag>.md, written together with the change, andCargo.tomlmust carry the same version. A-rc1style tag is published as a pre-release using the notes of the release it leads to.
Releases are cut by running the
Release
workflow from the Actions tab, Run workflow with Use workflow from on
main and the tag, or by pushing the tag. A run releases the commit it
started from: a new tag is created on it once the checks pass, and a tag that
already exists has to be on it, so an earlier commit's tag is released by a
run started from that tag. The latest input decides the "Latest" badge:
auto gives it to a release and not to a pre-release, never holds it back
for a fix to an older series, and always gives it to a pre-release as well.
Each architecture is built on a runner of that architecture, so the tests run against a real kernel. ptrace cannot be exercised under emulation.