publish-container fails on every push to main #34

New issue

Closed

opened 2026-10-17 02:08:42 +00:00 by agent-pi · 1 comment

agent-pi commented

2026-10-17 02:08:42 +00:00

Collaborator

Every push to main runs the publish-container job, which builds the container with VERSION taken from github.ref_name. On a push that value is main, so the Containerfile runs uv version --no-sync main and fails with "expected version to start with a number". The job only works on release events, where the ref is the tag (e.g. 0.1.0).

Net effect: every push to main shows a red run even when the release pipeline is fully green — seen on runs 1074, 1077, 1086, and 1091 (the 0.1.0 release push; its release-event run 1092 passed and published the image).

Wanted: publish-container should not run (or should degrade gracefully) when the event is not a release.

Spec: n/a — CI hygiene.

Every push to `main` runs the `publish-container` job, which builds the container with `VERSION` taken from `github.ref_name`. On a push that value is `main`, so the Containerfile runs `uv version --no-sync main` and fails with "expected version to start with a number". The job only works on `release` events, where the ref is the tag (e.g. `0.1.0`). Net effect: every push to main shows a red run even when the release pipeline is fully green — seen on runs 1074, 1077, 1086, and 1091 (the 0.1.0 release push; its release-event run 1092 passed and published the image). Wanted: `publish-container` should not run (or should degrade gracefully) when the event is not a release. Spec: n/a — CI hygiene.

agent-pi added the

Kind/Bug

Priority

Low

labels

2026-10-17 02:08:42 +00:00

agent-pi commented

2026-10-17 02:12:36 +00:00

Author

Collaborator

Plan of attack:

Gate the publish-container job to release events with if: github.event_name == 'release' (the same condition style pr-review already uses). On pushes the job shows as skipped, so main goes green; on releases nothing changes — the job still builds and publishes from the tag ref, as verified by run 1092.
The container build-and-smoke-test job stays enabled on both events: it succeeded on the push run, so it keeps providing pre-release image validation.

Branch: fix/issue-34-publish-container-release-only

Commits:

:bug: ci: run publish-container only on release events

PR: POST /repos/marvin8/xique/pulls (head fix/issue-34-publish-container-release-only, base main, Closes #34).

Plan of attack: - Gate the `publish-container` job to release events with `if: github.event_name == 'release'` (the same condition style `pr-review` already uses). On pushes the job shows as skipped, so main goes green; on releases nothing changes — the job still builds and publishes from the tag ref, as verified by run 1092. - The `container` build-and-smoke-test job stays enabled on both events: it succeeded on the push run, so it keeps providing pre-release image validation. Branch: `fix/issue-34-publish-container-release-only` Commits: - `:bug: ci: run publish-container only on release events` PR: `POST /repos/marvin8/xique/pulls` (head `fix/issue-34-publish-container-release-only`, base `main`, `Closes #34`).

agent-pi referenced this issue from a pull request that will close it,

2026-10-17 02:12:59 +00:00

Run publish-container only on release events #35

agent-pi closed this issue

2026-10-17 02:23:57 +00:00