Context
Next release after v0.1.0. Since v0.1.0, develop gained two user-facing feats — friendlier guided dataset push (#44) and dataset rm on the home screen + in-run guidance (#47) — plus the build.yml all-arch CI guard (#46). Two feat commits → minor bump per semver → v0.2.0.
Release infra (8-arch matrix, cosign signing, install scripts) is already in place from v0.1.0 — no workflow changes needed.
Scope
- README: Status line → v0.2.0; reconcile the Roadmap "Next (v0.2)" framing (cloud-sources etc. move to the next milestone, since v0.2.0 ships UX polish, not cloud ingestion).
- Pre-flight:
develop green (✓), all 8 targets cross-compile, go test -race ./....
- Tag
v0.2.0 off develop (no - → stable release).
Acceptance criteria
- README accurate for v0.2.0.
v0.2.0 published: 8 signed binaries + SHA256SUMS + install scripts; releases/latest → v0.2.0.
Context
Next release after
v0.1.0. Since v0.1.0,developgained two user-facingfeats — friendlier guideddataset push(#44) anddataset rmon the home screen + in-run guidance (#47) — plus the build.yml all-arch CI guard (#46). Twofeatcommits → minor bump per semver → v0.2.0.Release infra (8-arch matrix, cosign signing, install scripts) is already in place from v0.1.0 — no workflow changes needed.
Scope
developgreen (✓), all 8 targets cross-compile,go test -race ./....v0.2.0offdevelop(no-→ stable release).Acceptance criteria
v0.2.0published: 8 signed binaries + SHA256SUMS + install scripts;releases/latest→ v0.2.0.