ci(release): add develop→main Release-PR automation#135
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Adopt the Jarvus develop→main release flow. Pushing `develop` opens a "Release: vX.Y.Z" PR into main with a bot changelog (release-prepare); merging it tags vX.Y.Z (release-publish, via BOT_GITHUB_TOKEN so the tag can trigger downstream), which fires container-publish to build + push the GHCR image (:vX.Y.Z + :latest) — automating the previously-manual docker build. release-validate keeps the Release PR well-formed. ci.yml now also runs on develop. Workflows adapted from the jarvus-data-pipeline reference: single image (no sub-image/BigQuery), checkout@v6 + login-action@v3, no --platform (CI + cluster are amd64). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Also clarify in releases.md that release-validate guards main (only Release PRs target main; feature work goes to develop) — its failure on the bootstrap PR is expected. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Why
Stand up the Jarvus develop→main Release-PR flow so versioned releases are cut from a changelog'd PR, and the GHCR image build (currently a manual
docker build/push) is automated on tag.What
Four workflows + a
ci.ymltrigger update + operator docs:release-prepare.ymldevelopRelease: vX.Y.ZPR intomainwith a bot changelog (GITHUB_TOKEN)release-validate.ymlGITHUB_TOKEN)release-publish.ymlvX.Y.Z(BOT_GITHUB_TOKEN— required so the tag can trigger the next workflow)container-publish.ymlv*tag pushedghcr.io/codeforphilly/codeforphilly-ng:vX.Y.Z+:latestci.ymlnow also runs ondevelop.docs/operations/releases.mddocuments the flow.Adapted from the
jarvus-data-pipelinereference: single image (no sub-image/BigQuery),actions/checkout@v6+docker/login-action@v3, no--platform(CI runners + cluster are both amd64). The infra-components actions use the standard unpinnedchannels/.../latestrefs.After merge — operator steps (not code)
developoffmain(I'll do this once this lands).BOT_GITHUB_TOKENrepo/org secret is present (set) — required forrelease-publish.container-publishrun creates the package; grant the repo's Actions write access.main(recommended) — require PR + green CI.First push to
developwill propose v0.1.0 (no tags yet).🤖 Generated with Claude Code