Release and Version Policy¶
Defines how GCBM Assistant releases are produced and versioned.
Document Control¶
| Field | Value |
|---|---|
| Author | Geraldson Muluh |
| Owner | GCBM Assistant maintainers |
| Last reviewed | 2026-03-27 |
| Review cadence | Monthly |
Versioning Policy¶
- Application versions follow semantic-style tags (for example
v0.6.0). - Versioned releases represent explicit milestones and should have release notes.
- Continuous builds from
mainare pre-release artifacts for rapid validation.
CI/CD Channels¶
| Channel | Trigger | Output |
|---|---|---|
| Continuous | Push to main |
Updated pre-release installer asset |
| Versioned | Push tag matching v* |
Tagged release installer asset |
Documentation Version Expectations¶
- Docs on
mainrepresent the latest supported behavior. - Any workflow or command change must include docs updates in the same PR.
- CI docs quality checks must pass before merge.
Required Release Notes Content¶
Each versioned release should include:
- user-visible changes
- breaking or migration notes
- known limitations
- verification steps for installation and launch