Repository navigation
pump-v0.0.80
·
243 commits
to main
since this release
ci: split release tags into pump-v* and pump-cv-v* lines Iterating on the Go server / Android app was forcing a CV image "rebuild" (actually a manifest copy, but still pointless) on every tag bump and made the version numbers misleading. Splitting the tag lines fixes both: - container-publish.yml triggers on `pump-v*` only. The `pump-` prefix is stripped via docker/metadata-action's `type=match` pattern so the GHCR image tag stays clean (`pump:v0.0.80`, not `pump:pump-v0.0.80`). Retag-from-prior loop filters tags by the same prefix. - android-publish.yml also triggers on `pump-v*` (the Android app tracks the server's release line). A new "Compute version" step strips the prefix into steps.ver.outputs.version, used everywhere github.ref_name was — VERSION_NAME, APK filename, QR-code URL, QR commit message. The git tag (and therefore the GitHub Release object) keeps the prefix; only the user-visible version strings drop it. - cv-publish.yml triggers on `pump-cv-v*` only with the analogous prefix stripping. The two lines are completely independent — a Go-only `pump-v0.0.80` no longer touches the cv build, and a cv-only `pump-cv-v0.1.0` doesn't touch pump. Existing `v0.0.X` git tags pre-date the split and remain as historical markers — they no longer trigger any CI. The first tag in each new line falls through to a full rebuild (one-time cost); subsequent tags benefit from the rebuild-or-retag optimisation as before. CLAUDE.md updated with the new conventions and a cross-reference for the prefix-stripped image tag form. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>