ci(images): publish release and development images #26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/release-packages"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
x.y.ztags matching the project version, release created by a workflow) and the helm repo for publishing (REGISTRY_TOKEN, skip already-published versions, link each package to the repository).latest.Changes
Containerfile: multi-stagemix releaseon Debian trixie, runs as uid 65534,DBbuild arg selectssqlite3orpostgres.scripts/images.sh: shared build, push, retag and link logic; a version already in the registry is pulled and retagged, never rebuilt.scripts/release.shand.github/workflows/release.yml: on a bare version tag that equals themix.exsversion and is onmain, publishtraefik-control-sqlite3andtraefik-control-postgres, movelatestonly when the tag is the highest release, link the packages to the repo and create the release.scripts/development.shand.github/workflows/development.yml: every push to a branch other thanmainpublishes<version>-dev.<sha7>and movesdevelopment..dockerignoreand a README section describing the images, tags and release procedure.Verification
PUSH=0 ENGINE=podmanbuilds of both backends; SQLite image booted (migrations, login page and CSS 200, uid 65534); PostgreSQL image booted against a throwaway Postgres (22 migrations, login page 200).developmentand-dev.<sha>on both images;latestonly on the highest tag;mainand mismatched orv-prefixed tags rejected.shellcheck -xandactionlintclean.REGISTRY_TOKENwork), and the CI jobs passed.mix precommit(no Elixir changes).ci(release): publish container images on tagsto ci(images): publish release and development images