Release Management#
Turning a merged change into a versioned, immutable artifact — a container image, a GitHub Action or reusable workflow, a language package, a Terraform module — paired with a GitHub Release and a git tag, normally driven by pull-request labels. An implementation may add a GitHub-native ad hoc release path when its product needs one. No release CLI, no hand-edited version file, no tagging ritual.
| Page | Description |
|---|---|
| Spec | Requirements for release management — automatic, policy-driven, versioned releases driven entirely on the GitHub platform. |
| Design | How release management is built — a shared reusable workflow that resolves an explicit or configured SemVer bump, builds once, and publishes. |
| Publishing Targets | The contract every publishing destination documents, with GitHub Releases as the reference target. |