📚 docs(release): require dev promotion before tags - #469
Merged
Conversation
Route release preparation through dev before it can reach the stable main branch.\nRecord and freeze the release dev SHA to prevent unrelated commits entering a tag.\nDocument the promotion gate and the merge-commit topology used by the protected branches.
19 tasks
19 tasks
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
Document the protected release path so release preparation enters
dev, is promoted throughdev → main, and is tagged only from the verified stable merge. The repo-local$releaseskill now enforces the same sequence.Scope
Changes
release/<version> → dev → main → tagas the mandatory release branch flow.devSHA between the merged release PR and the promotion PR.User Impact
Release preparation now has an explicit, reproducible integration and promotion gate before a tag can publish packages or a GitHub Release.
Compatibility / Runtime Notes
Data / Security Notes
No credentials, runtime configuration, database data, or release secrets are changed. The documented source gate uses the existing same-repository
dev → mainpolicy.Risk / Rollback
Risk level: Low
Rollback notes:
Revert this documentation commit and restore the previous release procedure if the branch model changes.
Verification
Commands / evidence:
Screenshots / Recordings
N/A — release-process documentation only.
Docs
Docs decision:
docs/release.mdis the canonical repository release-process reference.Related
Refs #468