multimodThe missing cargo-release for Go

Unix-way CLI ecosystem for Go multi-module monorepos. Zero-config workspace sync, replace management, detached-commit releases, sub-module tagging. No YAML. No shell scripts. Just go.mod.

Getting Started

RFC-001

GitHub

🚧

Work In Progress

Honest status: RFC is solid, proof of concept works, dog-fooding is live. Not production-ready yet. We're building in public — the RFC drives development, not the other way around.

Read the RFC →

🔍

Zero Configuration

Directory structure is the config. A go.mod in a subdirectory = a sub-module. No YAML, no TOML, no .multimod.json. Discovery is automatic, deterministic, and auditable.

🔄

Always Synced

Every invocation guarantees the filesystem matches the desired state. go.work, replace directives, go version alignment — all synced. You cannot forget. You cannot drift.

🏷️

Detached-Commit Releases

Publish-state lives on a detached git commit behind a tag. Main never leaves dev-state. go get @v1.2.3 gets clean go.mod. Developers never see broken state.

How it works →

🔗

Unix Pipe Ecosystem

multimod modules | multirelease v1.2.3 --write --push. Each tool does one thing. JSON contracts between them. Any tool is replaceable with a shell script.

See the pipeline →

🚀

Dog-Fooding

multimod manages its own multi-module monorepo. The tool is built with the tool. If it breaks us, we fix it before it breaks you.

Read the origin story →