Releases¶
kwt uses semantic versions in vMAJOR.MINOR.PATCH form. It is still pre-1.0,
so minor releases may refine command or configuration contracts as the project
settles; upgrade notes call out changes that require attention.
How releases work¶
v0.4.0 is the first release produced by the automated artifact pipeline. It
is installable through Go:
Semantic-version tags run the full test suite and publish a GitHub Release with
platform archives, generated release notes, and checksums. v0.3.0 was the
first versioned tag, but predates that automated artifact pipeline.
The latest published version and its notes live on GitHub Releases. Install the newest tag available through the Go module proxy with:
See the changelog for the curated user-facing history.
Choosing a version¶
- Patch releases contain compatible fixes and documentation corrections.
- Minor releases add capability or intentionally revise a pre-1.0 contract.
- Major releases are reserved for a stable contract with explicit breaking changes.
Every release binary reports the version, source commit, build time, Go version, and target platform:
Maintainers can find the tagging checklist in Releasing kwt.