feat(release): pilot trunk-based CI/CD pipeline - #22
Merged
Merged
Conversation
Replaces release-train.yml with trunk-ci-cd.yml: every push to main builds one commit-addressed image (sha-<shortsha>/edge, no version bump) and sequences it through dev then pre. release.yml no longer rebuilds from source — it promotes an already-validated digest to a versioned stable release via docker-release.yml's new promote mode. Only one channel remains (stable); alpha/beta/rc are gone along with develop/staging. Pilot for the org-wide trunk-based-ci-cd proposal in sisques-labs/workflows#72/#73. Temporarily pinned to the workflows pilot branch until #72/#73 merge to main there.
sisques-labs/workflows#72 and #73 merged, so trunk-ci-cd.yml and docker-release.yml's promote mode now exist on main — drop the temporary pin to the pilot branch.
This was referenced Sep 16, 2026
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
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.
Summary
Pilots the org-wide trunk-based CI/CD proposal (sisques-labs/workflows#72, implementation in #73) in beacon-api, now that
develop/stagingare merged intomainand beacon-api is the first bounded-context template consumer.release-train.ymlwithtrunk-ci-cd.yml: every push tomainbuilds one commit-addressed image (:sha-<shortsha>,:edge— no version bump) and sequences it throughdeploy-dev→deploy-pre.release.ymlno longer rebuilds from source. It now takes asource_digestinput and usesdocker-release.yml's newbump_mode: promoteto retag an already-validated digest as the versioned stable release — the image that ships to prod is byte-for-byte what was validated inpre.stable);alpha/beta/rcare gone along withdevelop/staging.README.mdanddocker/README.mdto drop staledevelop/staging/prerelease references.Notes
sisques-labs/workflows@feat/trunk-based-ci-cd-01-pipelinein both workflow files (marked withTODO(trunk-based-ci-cd)) sincetrunk-ci-cd.ymlandbump_mode: promotedon't exist on that repo'smainyet. Must be re-pinned to@mainonce workflows#72/fix(deps): update dependency @apollo/server to v5 #73 merge.deploy-dev/deploy-preare placeholders (log-only) — no real dev/pre infrastructure exists yet. GitHub auto-creates thedev/preenvironments on first run (public repo, no protection rules needed to unblock this).develop/staging— if you want a required-reviewer gate onpreorprod, that's a separate Settings change.imagetools createpromotion) still needs a real dry-run before the first genuine prod release goes throughrelease.yml.Test plan
actionlintclean on both changed/added workflow filesnest build+vitest) passed@main