docs(release): propose trunk-based CI/CD design - #72
Merged
Merged
Conversation
Documents a proposed migration from branch-per-environment (develop/staging/main) to trunk-based development, where main is the only long-lived branch and dev/pre/prod promotion is driven by the pipeline instead of git merges. Additive only: no existing consumer of release-train.yml is affected until it opts in.
This was referenced Sep 14, 2026
JSisques
added a commit
to sisques-labs/beacon-api
that referenced
this pull request
Sep 16, 2026
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.
JSisques
added a commit
to sisques-labs/beacon-api
that referenced
this pull request
Sep 16, 2026
* feat(release): migrate to trunk-based CI/CD pipeline 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. * chore(release): repoint trunk-based workflows to workflows@main 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 17, 2026
Merged
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.
Summary
Proposes migrating the org's release model from branch-per-environment (
develop→alpha,staging→beta,main→stable, viarelease-train.yml) to trunk-based development: a singlemainbranch, withdev→pre→prodpromotion driven by the pipeline instead of git merges, and prod releases promoting an already-validated artifact by digest instead of rebuilding.This PR is documentation only (OpenSpec proposal + design + tasks) — no workflow code changes, no impact on any existing consumer of
release-train.yml. Beacon-api will pilot the actual implementation in a follow-up change once this design is agreed.See
openspec/changes/trunk-based-ci-cd/proposal.mdanddesign.mdfor the full rationale and decisions.Test plan