release

name	release
description	Tag-driven release automation — versioning, release types, and monitoring. Never create releases manually.

Release Procedures

Release System Overview

Releases are fully automated via CI. The workflow is:

1. Developer creates an annotated git tag
2. CI release workflow triggers, verifies, builds, and publishes
3. Update feeds or registries are refreshed automatically

Never create releases manually. Never use gh release create directly. If automation fails, fix the automation.

Versioning

Use semantic versioning. Version is determined entirely from git tags — no VERSION file.

• PATCH (0.6.4 → 0.6.5) — bug fixes, small improvements
• MINOR (0.6.5 → 0.7.0) — new features, backwards compatible
• MAJOR (0.9.0 → 1.0.0) — breaking changes, major milestones

Release Types

See the detailed procedure for each release type:

• stable.md — standard release from main
• beta.md — pre-release for testing
• hotfix.md — critical patch on a branch

Monitoring

gh run list --workflow=release.yml --limit 1
gh run watch <run-id>
gh release view v{VERSION}