feat(ci): publish the remo-web image for a pre-release (rc-image.yml) - #199
Merged
Merged
Conversation
The RC lane (dev-build.yml) builds a promotable wheel and attaches it to a GitHub pre-release under an `rc-*` tag, which release.yml (`tags: v*`) deliberately does not match. That left every pre-release with a wheel but no container image: ghcr.io/get2knowio/remo-web stops at the last `v*` release, so nothing Compose-based (e.g. a Hola catalog bundle on a `beta` channel) can pin an RC. Add rc-image.yml: builds docker/Dockerfile at a given ref with pyproject.toml stamped to the requested PEP 440 pre-release version (the same stamp dev-build.yml applies before `uv build`), pushes a multi-arch `ghcr.io/<owner>/remo-web:<version>` and prints the digest to the job summary for pinning. `latest` is never produced (flavor latest=false, single raw tag); final versions are refused so it can never shadow release.yml. Dispatchable on its own for an existing `rc-<version>` tag, and callable from dev-build.yml via a new `image=true` input (requires `prerelease=true`) so future RCs get wheel + image from the same commit. Nothing here publishes to PyPI or creates a tag. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Vck5KSX2CLxhohx14nb5Sh
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What / why
The RC lane (
dev-build.yml) produces a promotable wheel and a GitHub pre-release under anrc-*tag, whichrelease.yml(tags: v*) deliberately ignores. So a pre-release has a wheel but no container image:ghcr.io/get2knowio/remo-webstops at the lastv*release (4.3.6 today; the newest pre-release image tag is2.2.0-rc13). Nothing Compose-based can pin4.4.0rc1, including a Hola catalog bundle on a pre-release channel (try-hola/apps#149, try-hola/hola ADR 0005).Change
rc-image.yml(new):workflow_dispatch(version, optionalrefdefaulting torc-<version>) andworkflow_call. Validates a PEP 440 pre-release/dev version (final versions refused), checks out the ref, stampspyproject.tomlexactly asdev-build.ymldoes, and builds/pushesdocker/Dockerfileforlinux/amd64,linux/arm64asghcr.io/<owner>/remo-web:<version>, using the same pinned actions asrelease.yml.latestis never produced (flavor: latest=false, a single raw tag). The job summary prints the digest-pinned reference.dev-build.yml: newimageboolean input (requiresprerelease=true); a third job callsrc-image.ymlwith the build's version andgithub.sha, so future RCs get wheel + image from the same commit.CLAUDE.md/AGENTS.md: the two new invocations and one sentence in the RC paragraph.Nothing here publishes to PyPI or creates a tag.
Verification
yamlload: jobspublish-image;build,prerelease,image).gh workflow run rc-image.yml -f version=4.4.0rc1against the existingrc-4.4.0rc1tag after merge.🤖 Generated with Claude Code
https://claude.ai/code/session_01Vck5KSX2CLxhohx14nb5Sh