New GHCR packages come out public; say so
Document the registries scope and GHCR's default visibility
The cache purge is a workflow too Removes the last mention of Jenkins from the release process.
Everything is on Actions now The container, the Helm chart and the PyPI upload have moved, so no part of the release process runs from Jenkins. The chart now goes to GHCR, and the container to both Docker Hub and GHCR, with Docker Hub remaining canonical.
Note that PyPI is also still on Jenkins The wheel is built, published to the candidate and installed by the acceptance test, but nothing uploads it to PyPI; that remains a separate Jenkins job run after promotion, alongside the container and the Helm chart.
Rewrite the release procedure for the Actions pipeline The old procedure described the Jenkins buildfarm and required being on a particular corporate network. Building and publishing now run on GitHub Actions, so anyone with write access to the repository can do it. What changed beyond the job names: candidates test themselves, so there is an explicit statement that a red acceptance test means a new candidate rather than a repair; promotion takes a scope, so the steps that cannot be undone are named as such; and the container images and Helm chart are flagged as still running from Jenkins. Also adds an index page.
Initial Home page