Create Release

Overview

Prepare a release by updating CHANGELOG (promote [Unreleased] to the new version with date), committing that change, then creating an annotated git tag. The release workflow (triggered by pushing the tag) reads the CHANGELOG section from the tagged commit for GitHub release notes and updates docs/releases.md on main itself—so only CHANGELOG is updated before the tag.

Definitions

• {VERSION}: Release version following semantic versioning (e.g., v1.0.0, v1.1.0, v2.0.0)
  • Must start with v prefix
  • Format: vMAJOR.MINOR.PATCH
• Tag Message: Simple commit message in format: Release {VERSION} - {DATE}

Prerequisites

Before proceeding, verify:

1. Working Directory: Ensure you're in the repository root directory
   • If not in repository root, STOP and change to repository root directory.
   • Git Operation Standards: Git operations should follow best practices. These standards are documented in AGENTS.md §3 Operational Boundaries if AGENTS.md exists, but apply universally regardless.