docs: prepare v0.3.0 release (COD-388) - #45
Conversation
- Bump version constants to 0.3.0 (cmd/root.go, internal/mcp/server.go) - Add CHANGELOG.md covering 0.3.0, 0.1.0, and the superseded pre-reset 0.2.0 - README: document gemini/copilot/opencode targets, validate/doctor/diff, config management commands, and pinned-release install example v0.2.0 is burned: the tag points at pre-reset commit 1e72b0d (an ancestor of v0.1.0), is published in the Go module proxy, and is pinned by sum.golang.org records, so the number cannot be reused. Release as v0.3.0 instead; do not install the stale v0.2.0.
🤖 Automated Review PanelReviewer A (dual-model panel)Verified against the live repo: read the diff, built the binary ( Findings: no blocking issues. Docs + two version constants only; no behavior change. Flagged that Reviewer B (dual-model panel)Independently verified the diff claims: ran the full verification suite (build/vet/fmt/test -race — all pass), checked the CHANGELOG prose against actual code ( Findings: no blocking issues; no convention violations. Panel verdict: clean. Both reviewers verified empirically rather than trusting the diff text. Pinned-install example, positional-arg command syntax, and manifest example all match real CLI behavior. |
Auto-Merge Gate — SKIP (policy) 2026-08-19Skipped by the gate, not on quality:
Ready for your review/merge. On merge, the next runner run executes the release checklist (tag, release, install verification) and closes COD-388. |
Auto-Merge Gate — Approval (2026-08-19)Confidence: 0.92 — MERGE (squash) PR goal (COD-388, release-prep slice): package v0.3.0 — version constants, CHANGELOG, README support/quick-start updates. Why it satisfies the release-prep slice:
Checks observed: Test SUCCESS, Lint SUCCESS, Secret Scan SUCCESS. Policy check: creed Post-merge obligations (explicitly NOT done by this merge): COD-388 remains open — tag Scope limits: 4 files +104/−2. No secrets, no deployment/cutover, no destructive behavior, same-repo branch (owner TechGodHQ, author shivros). Self-authored PR — formal self-approval rejected by GitHub; this comment is the approval rationale and audit artifact. |
1 participant
Summary
Release prep for v0.3.0 (COD-388, P0). All five v0.2 feature dependencies (watch, diff, config management, validate, doctor) are merged to main; this PR packages the release.
Why v0.3.0 and not v0.2.0: the
v0.2.0tag is burned. It points at pre-reset commit1e72b0d(2026-07-07, an ancestor of the v0.1.0 release commit), it is published in the Go module proxy pinned to that hash, and sum.golang.org holds signed immutable records for it. Retagging would break checksum verification for anyone who ever fetched v0.2.0. The issue scope says "retag only if explicitly necessary and safe" — it is neither necessary nor safe. Per semver, skipping a burned version is standard practice.Changes
cmd/root.go,internal/mcp/server.go: version constants0.1.0→0.3.0(CLI--versionand MCP server implementation version)CHANGELOG.md(new): full 0.3.0 release notes — generated interaction surfaces, MCP stdio server, gemini/copilot/opencode targets, watch/diff/validate/doctor/config management, git remote hardening — plus honest history for 0.1.0 and the superseded pre-reset 0.2.0README.md: support table rows for GitHub Copilot and OpenCode; quick-start examples forvalidate/doctor/diff/ config-management commands (positional-arg syntax verified against--helpoutput); pinned-release install example (@v0.3.0); manifest example includes all 9 scaffolded targetsVerification (this run, on the release commit)
go build ./...✅go vet ./...✅gofmt -l .→ clean ✅go test -race -count=1 ./...→ all packages ok ✅ (also re-run by lefthook pre-commit)scripts/check-generated.sh→ generated code current ✅go run . --version→creed 0.3.0✅--help+ real invocation (diff --target claudeproduced real diff output) ✅Post-merge (next runner run, on the merge commit)
v0.3.0on the merge commitgo install github.com/techgodhq/creed@v0.3.0from a clean module cacheDraft until the tag/release/install verification can run post-merge.