Composable governance CLI for Go projects.
Version determination, release notes, cross-compilation, pre-publish staging, dev-state sync. For single-module and multi-module projects. No YAML DSL. No monolithic pipeline. No paywall on composable features. Unix-way subcommands, structured stdout, every step replaceable.
Work in progress. Architecture under active RFC development — stress-tested through adversarial review. Previously named
multimod— renamed togoverafter scope expansion.
Library? gover bump → gover release --write --push → gover notes | gh release create. Tags, publish-state, release notes.
CLI tool? Add gover build for cross-compile + archive + checksum. Full pipeline.
Multi-module? gover (root command) syncs go.work, replace directives, Go version. Then everything above.
go install github.com/thumbrise/gover@latest
goverOne command. After this: go.work is correct, replace directives are in place, Go version is aligned, IDE works, go test ./... covers all modules. Run it again — nothing changes. Idempotent.
thumbrise.github.io/gover — getting started, RFC, devlog.
- Getting Started — install, first sync
- Reference — RFCs: architecture, design decisions, disputed points
- Devlog — design decisions, dead ends, lessons learned
Born inside thumbrise/resilience. Read the full story.
Apache 2.0