---
roadcrew_template_name: "release.template.md"
roadcrew_template_type: "template"
roadcrew_template_version: "v1.0"
roadcrew_last_updated: "2025-01-25"
roadcrew_min_version: "1.5.0"
roadcrew_license: "Apache-2.0"
roadcrew_copyright: "Copyright (c) 2025 North Star Holdings, LLC"
spdx_license_identifier: "Apache-2.0"
name: Release
about: Track a major or minor release with all epics and child issues
title: "[Release v{{VERSION}}] {{RELEASE_NAME}}"
assignees: {{ASSIGNEES}}
---
## Release v{{VERSION}}: {{RELEASE_NAME}} - {{STATUS}}

<!-- GitHub Issue: #{{RELEASE_GITHUB_ISSUE}} (populated by scope-release) -->

### Overview

**Current State ({{PREVIOUS_VERSION}})**:
<!-- MAX: 30 words -->
{{CURRENT_STATE}}

**Target State ({{VERSION}})**:
<!-- MAX: 30 words -->
{{TARGET_STATE}}

### Child Epics
{{EPIC_CHECKLIST}}

### Release Criteria
{{RELEASE_CRITERIA}}

### Dependencies
- **Depends on:** {{DEPENDENCY_RELEASES}}
- **Blocks:** {{BLOCKED_RELEASES}}

### Definition of Done

- [ ] All epics completed and closed

---

### Epics

#### EPIC {{EPIC_NUMBER}}: {{EPIC_TITLE}}

<!-- STRUCTURE: templates/epic.template.md - All sections from that template apply here, including embedded child issues -->
<!-- GitHub Issue: #{{EPIC_GITHUB_ISSUE}} (populated by scope-release) -->

---

<!-- 
TEMPLATE REFERENCE:

This template serves dual purposes:
1. GitHub Release tracking issue (YAML frontmatter controls issue creation)
2. Document structure for current-release.md and future-releases.md

Epic sections (with embedded issues) → templates/epic.template.md

GitHub Issue Numbers:
- Populated by /scope-release when creating issues
- Format: <!-- GitHub Issue: #123 --> in comment for parsing
- Only applicable to current-release.md (future releases don't have issues yet)
-->