20146c8eae
All checks were successful
sync-to-forgejo / sync (push) Successful in 15s
The $imagepolicy marker was still present on this line, so FluxCD Image
Automation kept overwriting CI's digest-pinned image every ~2 minutes
with whatever it considered alphabetically "highest" (":latest" beats
any hex SHA tag under an ascending-alphabetical policy) - the exact
race the ai-assistant build.yaml's own comments describe having fixed,
but the marker was never actually removed for this app specifically.
admin-solid and frontend-solid don't carry this marker, which is why
their CI-driven digest pins hold; bring ai-assistant in line with that
convention so its build.yaml "Update GitOps" step is the sole writer
going forward.
Pinned to the digest currently running in the cluster
(sha256:106d0403...) after a manual rollout restart picked up
today's security-fix build.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| ai-guard | ||
| forgejo | ||
| github-actions-runners/base | ||
| litellm | ||
| nxtgauge-admin-solid | ||
| nxtgauge-ai-assistant | ||
| nxtgauge-backend-rust | ||
| nxtgauge-frontend-solid | ||
| ollama/base | ||
| postgresql | ||
| registry | ||
| traceworks2026 | ||