Releases: govctl-org/govctl
v0.8.4
govctl v0.8.4
Added
- Write-time gate blocks adr set/edit decision when alternatives incomplete (WI-2026-04-14-001)
- Lifecycle gate blocks adr accept for incomplete ADRs (WI-2026-04-14-001)
- adr accept --force bypasses lifecycle gate for historical backfills (WI-2026-04-14-001)
Full Changelog: v0.8.3...v0.8.4
v0.8.3
govctl v0.8.3
Added
- Implement govctl self-update command with --check flag (WI-2026-04-13-001)
- Add cargo-binstall metadata to Cargo.toml (WI-2026-04-13-001)
Full Changelog: v0.8.2...v0.8.3
v0.8.2
govctl v0.8.2
This release adds first-class controlled-vocabulary tags for governance artifacts and fixes a regression in clause text editing.
Added
tagsfields are now available on all five artifact types: RFC, clause, ADR, work item, and guard.- Added
govctl tag new,govctl tag delete, andgovctl tag list, including usage counts. govctl checknow validates artifact tags against the configured allowed tag list.- Added
--tagfiltering onrfc,clause,adr,work, andguardlist commands.
Fixed
govctl clause edit <ID> text --stdinnow works without requiring an explicit--set.
Upgrade Notes
- No artifact format migration is required for this release.
- If you want to use controlled tags, configure the allowed tag list in your project and then apply tags through the new tag commands.
v0.8.1
govctl v0.8.1
This is a patch release focused on Codex agent generation ergonomics.
Added
--format codexnow writes.tomlagent files withdeveloper_instructions.--dirnow overrides the output directory directly, without requiring config edits.
Upgrade Notes
- No migration step is required for existing repositories.
- This release does not change governance artifact formats or release workflow contracts.
v0.8.0
Breaking Changes
- RFC and Clause legacy JSON write paths are no longer supported.
- RFC/Clause mutation and lifecycle operations now assume TOML as the canonical writable format.
- Repositories that still contain legacy JSON RFC or clause artifacts must run
govctl migratebefore using those commands.
This is why this release is 0.8.0 rather than a patch release: it introduces a public CLI capability expansion and a breaking change in legacy artifact handling.
Highlights
- Introduced the canonical path-first edit surface:
govctl <resource> edit <ID> <path> --setgovctl <resource> edit <ID> <path> --addgovctl <resource> edit <ID> <path> --removegovctl <resource> edit <ID> <path> --tick
- Routed existing
set/add/remove/tickverbs through the same canonical edit planning path. - Generalized nested edit resolution so object and array paths work at arbitrary supported depth.
- Simplified command planning and hardened CLI help so help text is a more reliable agent-facing contract.
- Kept the canonical edit surface while rejecting the heavier ADR schema redesign;
ADR-0038supersedesADR-0036.
Fixed
- Converted command paths now emit explicit
DiagnosticCodevalues with stable formatting for automation. - User-facing expected failures no longer fall back to temporary uncoded
anyhowmessages. - Legacy JSON-only RFC/clause lifecycle commands now fail with a migrate-first diagnostic instead of a misleading not-found error.
- Concurrency and lock behavior for canonical edit paths were tightened and regression-tested.
Upgrade Notes
- If your repository is already on TOML-governed artifacts, no special migration step is needed.
- If you still have legacy JSON RFC or clause artifacts, run:
govctl migratebefore attempting RFC/clause edit or lifecycle operations.
Full Changelog: v0.7.7...v0.8.0
v0.7.7
TUI is now enabled by default in release binaries.
Full Changelog: v0.7.6...v0.7.7
v0.7.6
TUI is now enabled by default in release binaries.
Full Changelog: v0.7.5...v0.7.6
v0.7.5
TUI is now enabled by default in release binaries.
Full Changelog: v0.7.4...v0.7.5
v0.7.4
TUI is now enabled by default in release binaries.
Full Changelog: v0.7.3...v0.7.4
v0.7.3
TUI is now enabled by default in release binaries.
Full Changelog: v0.7.2...v0.7.3