Topic
Everything filed under software-delivery, across every section.
Use an annotated Git tag as the immutable version marker, then turn it into a GitHub release page with reviewable notes and downloadable assets. This runbook shows the exact sequence, checks, and decisions for publishing a version without losing the connection between code and artifacts.
Turn release management into a repeatable, executable checklist with test evidence, named approvers, deployment ownership, measurable rollback triggers, and post-release verification.
Use GitHub Actions artifacts for short-lived CI evidence and job-to-job handoffs, then publish only scanned, approved distributables as GitHub Release assets. This worked pipeline shows where the boundary belongs, how retention changes the decision, and how to enforce it.