jarvis e19013ed5e fix(ci): image pushes read the registry secrets that exist (#1275) ...

All kaniko image steps (publish.yml build-gateway/build-ci-base/build-*
and ci-image.yml build-ci-base) referenced from_secret: gitea_username /
gitea_password - which do not exist at repo level - while the repo
carries unused REGISTRY_USERNAME/REGISTRY_PASSWORD secrets. Result: every
image push fails at kaniko's push-permission check (measured: 2482 and
2488 build-gateway 'error checking push permissions'; the same auth gap
is documented in ci.yml's step-level pi install comment re ci-base).

Rewire all six references to the REGISTRY_* secrets that exist. If those
credentials are valid, next push pipelines go fully green behind the new
verify gate; if not, the failure moves to an explicit 401 - either way
the ambiguous permission error resolves into a known state.

2026-08-17 23:50:29 -05:00

..

ci-image.yml

fix(ci): image pushes read the registry secrets that exist (#1275)

2026-08-17 23:50:29 -05:00

ci.yml

feat(ri-050): bind next publication to exact-commit terminal verification — RI-1-001 (#1275) (#1277)

2026-08-18 03:57:43 +00:00

publish.yml

fix(ci): image pushes read the registry secrets that exist (#1275)

2026-08-17 23:50:29 -05:00