Repository navigation
Releases
v1.2.2
v1.2.1
v1.2.0
v1.1.0
Fixes found onboarding the template's first consumer. Additive — no interface changes, so ?ref= and uses: …@ bumps are drop-in from v1.0.0.
Per-arch build tags no longer shadow the release tag
The matrix pushed <version>-amd64 / <version>-arm64 and joined them into <version>. All three sort identically under a Flux ImagePolicy anchored on the version prefix, so ImageUpdateAutomation could pick a per-arch tag — a single-arch image that will not run on the other architecture's nodes. Observed in practice, self-correcting only by luck of ordering.
Scaffolding tags are now buildstage-<arch>-<version>. Version last means an anchored filter cannot match them; Go RE2 has no lookahead, so excluding the suffix in-pattern was not possible.
Upgrading: nothing to change if your filterTags pattern is anchored with ^. Old <version>-<arch> tags from previous releases stay in the registry and are harmless — delete them if you want the package tidy.
Cache export failure no longer fails the build
cache-to: type=registry writes into the project's own GHCR package. A failed cache export failed the whole run even after the image pushed successfully — which is what a first-ever deploy does, since there is no package yet. ignore-error=true on all three workflows.
Documentation
- The four tags a release publishes and which one is deployable.
- The GHCR package permission model: an unlinked package is hidden from the repository's Packages tab, so it looks absent, and granting
packages: writedoes not help because the token is not what is being refused. general-secretsdoes not createghcr-login-secretin every app namespace — it is a hand-maintained per-cluster list, and a missing entry fails as an anonymous pull with401.