Guide new project release

Guide new release creation with version bump and changelog

Creating a release tag and version bump with a full audit trail and zero-trust approval gates

• · Current version from pkg/api/version.txt or git tag
• · New version (explicit version, semver bump type, or user selection)
• · Git log since last release for changelog

• · Updated pkg/api/version.txt with new version
• · Updated CHANGELOG.md with release notes
• · Git commands for commit, tag, and push (requires explicit user approval before executing)

• · Read (pkg/api/version.txt, CHANGELOG.md, git log)
• · Write (version file, CHANGELOG.md)
• · Bash (git tag, git log, make lint/sec/test/build commands)

• · pkg/api/version.txt or git tags present for version tracking
• · CHANGELOG.md exists in project root
• · Git repository initialized
• · All pre-commit checks (lint, sec, vulncheck, tests) passing

• · Version parse ambiguous (no current version found)
• · Pre-commit checks fail (tests, linting, security scans)
• · User declines version confirmation or final release confirmation

• · Requires explicit approval at THREE checkpoints (version, release commands, final go-ahead)
• · Runs full pre-commit checklist (make lint, make sec, make vulncheck, make test, make build)
• · Shows exact git commands before executing (no surprises)
• · Categorizes commits (Features, Fixes, Improvements, Docs, Internal)
• · Pre-release suffix handling (e.g., 0.1.3-alpha + patch → 0.1.4-alpha)