feat(release): implement trunk-based CI/CD pipeline - #73
Merged
Merged
Conversation
JSisques
changed the base branch from
docs/trunk-based-ci-cd-design
to
main
September 16, 2026 08:57
Adds trunk-ci-cd.yml (continuous build + dev/pre deploy, sequenced via needs:) and a promote bump_mode in docker-release.yml that retags an already-validated digest instead of rebuilding, so prod ships byte-for-byte what passed pre. Purely additive: release-train.yml and the legacy/release-train bump modes are untouched, and release-train-detect's regression suite still passes (36/36). Multi-arch imagetools promotion is flagged in tasks.md as not yet dry-run validated.
JSisques
force-pushed
the
feat/trunk-based-ci-cd-01-pipeline
branch
from
September 16, 2026 08:58
c0c0267 to
ba1fb24
Compare
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
Implements the design proposed in #72:
trunk-ci-cd.yml(continuous build, commit-addressed tags, sequenceddeploy-dev→deploy-pre) and a newbump_mode: promoteindocker-release.ymlthat retags an already-validated digest instead of rebuilding from source, so a prod release ships byte-for-byte what passedpre.Purely additive:
release-train.ymland the existinglegacy/release-trainbump modes are untouched.release-train-detect's regression suite still passes (36/36).actionlintis clean on both changed workflow files.deploy-dev/deploy-preare placeholder steps — no consuming repo has real dev/pre infrastructure yet (seedesign.mdD4); the job graph and ordering are the deliverable here.Chain Context
docs/trunk-based-ci-cd-designdocs/trunk-based-ci-cd-design(design merged into this branch)trunk-ci-cd.yml+docker-release.ymlpromote mode ready for a pilot repo to consumeChain Overview
Scope
trunk-ci-cd.yml,docker-release.ymlbump_mode: promote, README docs,tasks.mdprogressrelease-train.ymlAutonomy
imagetools createpromotion is flagged but not yet dry-run validated (tasks.md 2.4/2.5, 4.2)Test plan
actionlintclean ontrunk-ci-cd.ymlanddocker-release.ymltests/release-train-detect.test.sh— 36/36 passing, no regressiontrunk-ci-cd.ymlend-to-end against a disposable repo (tasks.md 4.1)docker-release.ymlbump_mode: promoteagainst a real multi-arch image (tasks.md 4.2)