ci: build+push image only on main merge or release tag #137

Merged

fastie81 merged 1 commit from ci/build-on-merge into main

2026-09-06 17:35:39 +12:00

fastie81 commented

2026-09-06 17:35:25 +12:00

Owner

Gates the image build+push to main merges and v-tag releases only.

Before: every feature-branch push ran the build job (docker buildx, docker login, image push of a disposable ci-, registry prune).

After: branch/PR pushes run only test + lint-frontend for fast feedback. The build job (and its push + prune) fires only on:

main (deploy to test node)
v tags (promote test -> prod)

deploy already needs build and gates on the same condition, so a broken Dockerfile/requirements change is still caught by deploy's need:build before anything is released -- no prod risk. No image is ever pushed or pruned on a non-release branch.

Verified on this branch: test 2m16s, lint 58s; build + deploy correctly skipped.

Gates the image build+push to main merges and v-tag releases only. Before: every feature-branch push ran the build job (docker buildx, docker login, image push of a disposable ci-<sha>, registry prune). After: branch/PR pushes run only test + lint-frontend for fast feedback. The build job (and its push + prune) fires only on: - main (deploy to test node) - v<semver> tags (promote test -> prod) deploy already needs build and gates on the same condition, so a broken Dockerfile/requirements change is still caught by deploy's need:build before anything is released -- no prod risk. No image is ever pushed or pruned on a non-release branch. Verified on this branch: test 2m16s, lint 58s; build + deploy correctly skipped.

fastie81 added 1 commit

2026-09-06 17:35:27 +12:00

ci: only build+push the image on main merge or v-tag release

CI / test (push) Successful in 2m16s

Details

CI / lint-frontend (push) Successful in 58s

Details

CI / build (push) Has been skipped

Details

CI / deploy (push) Has been skipped

Details

cb749f1441

Branch/PR pushes now run just test + lint-frontend for fast feedback.
The build job (and its image push + registry prune) only fires on:
  - main (deploy to test node)
  - v<semver> tags (promote test -> prod)

Previously every feature-branch push built and pushed a disposable ci-<sha>
image. deploy already gates on the same condition and needs build, so a
broken Dockerfile is still caught before anything deploys - no prod risk.

Caching was confirmed already live (runner internal cache server enabled,
1.2G in /root/.cache/act): actions/cache (pip), setup-node (npm) and Docker
inline layer cache all persist across runs, so no cache change needed.

fastie81 merged commit 955608f3e0 into main

2026-09-06 17:35:39 +12:00

fastie81 referenced this pull request from a commit

2026-09-06 17:35:43 +12:00

Merge pull request 'ci: build+push image only on main merge or release tag' (#137) from ci/build-on-merge into main