jcoffey-dev bdee5de814 ci: copy each release image to GHCR as a replica ...

The Gitea registry stays authoritative; GHCR becomes a copy of it, the way
the GitHub repository is a copy of the Gitea one. After the tag build has
pushed the release image to the registry, a new ghcr job copies it to
ghcr.io under the same version tag and :latest with `imagetools create` --
a copy, not a rebuild, so the digest on GHCR is the digest on the registry.

Anything still pulling the old ghcr.io name, including the TrueNAS app
submission, keeps receiving releases. The job uses the run's own token and is
left out of the status reported to Gitea, so a GHCR problem cannot fail a
release.

2026-09-30 09:27:48 -07:00

..

ci.yml

ci: copy each release image to GHCR as a replica

2026-09-30 09:27:48 -07:00