Follow-up to #15. The release pipeline (.goreleaser.yaml, signed GitHub Actions workflow on tag push, cosign keyless, Syft SBOMs, pre-release marker) is already in place from the v0.1.0-alpha.1 cycle — this issue tracks cutting the next alpha once the v0.2.0 backlog lands.
- Tag
v0.2.0-alpha.1 (semver pre-release identifier).
- CHANGELOG entry under
[0.2.0-alpha.1] describing the alpha scope: write endpoints, multi-profile management, session writes; remaining gaps and breaking-change posture before v0.2.0.
- README badge for latest pre-release continues to track the new tag (no code change expected — the badge URL points at the latest pre-release).
- Verify goreleaser snapshot still produces the expected artefacts (binaries × OS/arch matrix, deb/rpm, cosign signatures, SBOMs) on the pre-tag dry run.
Blocked by the v0.2.0 write-side work: #13 (write operations), #60 (session writes), #39 (multi-profile). #82 (AUR PKGBUILD + Homebrew tap) is independent — can land before or alongside the alpha. The stable v0.2.0 release is out of scope for the alpha; expect breaking changes between the alpha and the stable tag.
Follow-up to #15. The release pipeline (
.goreleaser.yaml, signed GitHub Actions workflow on tag push, cosign keyless, Syft SBOMs, pre-release marker) is already in place from the v0.1.0-alpha.1 cycle — this issue tracks cutting the next alpha once the v0.2.0 backlog lands.v0.2.0-alpha.1(semver pre-release identifier).[0.2.0-alpha.1]describing the alpha scope: write endpoints, multi-profile management, session writes; remaining gaps and breaking-change posture beforev0.2.0.Blocked by the v0.2.0 write-side work: #13 (write operations), #60 (session writes), #39 (multi-profile). #82 (AUR PKGBUILD + Homebrew tap) is independent — can land before or alongside the alpha. The stable
v0.2.0release is out of scope for the alpha; expect breaking changes between the alpha and the stable tag.