feat(deploy): publish :latest when the image script runs over main #117

Merged
EduarD3V merged 1 commit from hotfix/latest-tag into agent-develop 2026-10-10 16:57:05 +02:00
Owner

Summary

scripts/publish-container-images.sh accepts a main ref and pushes the moving :latest tag for all four images; a v[0-9]* run keeps pushing the immutable version tag. A main build is stamped with git describe --tags --always (never the floating main ref, which the agent refuses per UC-AG-20). Any other ref still exits 1.

No CI job changes: re-verified 2026-10-10 that Forgejo job containers have no Docker CLI/socket/CAP_SYS_ADMIN, so images stay out-of-band.

Smoke

Faked docker on PATH:

  • GITHUB_REF_NAME=main → :latest for all four images, GOTOI_VERSION=v0.2.1-2-g605998e
  • GITHUB_REF_NAME=v0.2.1 → version tags, unchanged
  • GITHUB_REF_NAME=feature/x → exit 1

Gates

_check.py 380 UC conform; check-ai-headers.py 587 ok; check-type-mirror.py exit 0; docker compose config --quiet exit 0; footer guard empty.

UC-OP-27

## Summary `scripts/publish-container-images.sh` accepts a `main` ref and pushes the moving `:latest` tag for all four images; a `v[0-9]*` run keeps pushing the immutable version tag. A `main` build is stamped with `git describe --tags --always` (never the floating `main` ref, which the agent refuses per UC-AG-20). Any other ref still exits 1. No CI job changes: re-verified 2026-10-10 that Forgejo job containers have no Docker CLI/socket/`CAP_SYS_ADMIN`, so images stay out-of-band. ## Smoke Faked `docker` on `PATH`: - `GITHUB_REF_NAME=main` → `:latest` for all four images, `GOTOI_VERSION=v0.2.1-2-g605998e` - `GITHUB_REF_NAME=v0.2.1` → version tags, unchanged - `GITHUB_REF_NAME=feature/x` → exit 1 ## Gates `_check.py` 380 UC conform; `check-ai-headers.py` 587 ok; `check-type-mirror.py` exit 0; `docker compose config --quiet` exit 0; footer guard empty. UC-OP-27
feat(deploy): publish :latest when the image script runs over main
All checks were successful
CI and agent release / check-docs (pull_request) Successful in 25s
agent-guards / test-tampering (pull_request) Successful in 41s
CI and agent release / preflight (pull_request) Successful in 44s
CI and agent release / test-agent (pull_request) Successful in 1m37s
CI and agent release / test-dashboard (pull_request) Successful in 2m29s
CI and agent release / test-middleware (pull_request) Successful in 9m37s
CI and agent release / build (pull_request) Has been skipped
CI and agent release / release (pull_request) Has been skipped
6468977033
`scripts/publish-container-images.sh` now accepts a `main` ref and pushes the
moving `:latest` tag for all four images (middleware, dashboard, docs,
marketing); a `v[0-9]*` run keeps pushing the immutable version tag. A `main`
build has no version of its own, so the images are stamped with
`git describe --tags --always` rather than the floating `main` ref the agent
refuses. Any other ref still exits 1.

Images are built out-of-band: the Forgejo runner gives job containers no Docker
CLI, socket, or `CAP_SYS_ADMIN` (re-verified 2026-10-10), so there is no
image-building CI job to change.

Smoke: faked `docker` on PATH exercised all three paths — `main` → `:latest`
with stamp `v0.2.1-2-g605998e`, `v0.2.1` → version tags, `feature/x` → exit 1.

Docs and policy updated to match: UC-OP-27, CHANGELOG, RELEASING_INSTRUCTIONS,
deploy/README.md, docs/DEPLOY-K8S.md, docs-site deploy.mdx, .agents/features.md.

UC-OP-27
EduarD3V changed target branch from develop to agent-develop 2026-10-10 16:46:15 +02:00
EduarD3V changed target branch from agent-develop to develop 2026-10-10 16:48:47 +02:00
EduarD3V changed target branch from develop to agent-develop 2026-10-10 16:56:45 +02:00
EduarD3V merged commit 6dd0a31c54 into agent-develop 2026-10-10 16:57:05 +02:00
Sign in to join this conversation.
No description provided.