Releasing kwt¶
Coordinate publication with the release operator. This repository does not publish release artifacts when a tag is pushed. Do not create a tag or GitHub Release separately from the release process.
Before publication¶
- Start from the exact commit on
mainthat should be released. - Confirm the branch is clean and the intended CI checks passed.
- Run
make test,make build, andmake docs-checklocally. - Review the changes since the previous tag and choose the next semantic version. Because kwt is pre-1.0, user-visible contract changes normally require a minor version.
Release identity¶
Each release must use a new annotated semantic-version tag at the approved source commit. Never move or replace a published tag or its artifacts.
Daemon build identity includes the full source revision and its source commit
time. The source time must be canonical RFC3339 UTC and must not be a package,
archive, or local build timestamp. Ordinary Go builds fall back to the embedded
vcs.time. Build systems that stamp a pinned revision explicitly, including
Ghosthub's managed helper build, must also pass its resolved source time:
Release builds must stamp the same field from the tagged commit date.
Verify the result¶
On the GitHub Releases page, confirm that the release contains archives for macOS, Linux, and Windows on AMD64 and ARM64, plus a checksum file. Download one archive for the current platform, verify its checksum, and run:
If publication fails, preserve the tag and existing artifacts while the release operator investigates. If the source needs a fix, merge it and use a new version.