Skip to content

v0.10.0

Choose a tag to compare

@marcelocantos marcelocantos released this 01 Jun 08:55
· 4 commits to master since this release
e5f5219

Headline: the project formerly known as mk is now cv.

Pure rename release — no behaviour changes, no new features. The name cv (short for converge) reframes the tool around its core function: drive a project toward a declared state, with cv as the imperative verb. Pairs naturally with bullseye (the target system) and the /cv skill (which audits convergence) for a shared vocabulary across the convergence toolchain.

Why rename

Plan 9 mk (Andrew Hume & Bob Flandrena, 1989) is a build tool of the same category, using the same mkfile filename, with 35+ years of prior art. Disambiguating dissolves the PATH/discoverability conflict and lets us acknowledge Plan 9 mk explicitly as the predecessor — many of mk's design choices ($target style metavariables, parallel-by-default, oneshell-by-default, mkfile convention) were independent re-derivations of decisions Plan 9 mk made first. The lineage is preserved verbatim in DESIGN.md, docs/why-cv.md, and docs/discovered-dependencies.md.

Scope of the rename

  • Go package mk → cv; module github.com/marcelocantos/mk → github.com/marcelocantos/cv. (Old URL redirects.)
  • Binary cmd/mk → cmd/cv; output cv.
  • Conventional file mkfile → cvfile.
  • State directory .mk/ → .cv/.
  • Stdlib files std/*.mk → std/*.cv; embed directive updated.
  • Shell completions completions/cv.bash, completions/cv.zsh; functions renamed to _cv.
  • CI workflow: ldflags target, tarball naming, Homebrew formula install/test blocks, completion install paths.
  • Old Homebrew formula Formula/mk.rb deleted from marcelocantos/homebrew-tap. This release creates Formula/cv.rb.

For existing mk users (i.e., me)

brew uninstall mk
brew update
brew install marcelocantos/tap/cv

No on-disk state needs migration: .mk/ directories from prior builds are simply ignored by cv and can be deleted at leisure. Old mkfiles need to be renamed to cvfile (or you can run cv -f mkfile to keep the old filename per-project).

What's not changing

  • The DESIGN.md spec — the language, semantics, and engine are unchanged from v0.9.0.
  • The discovered-dependency model (DESIGN.md §11) shipped in v0.9.0 — still here, still working, still self-healing on deleted headers.
  • The release-tag history. v0.1.0–v0.9.0 of the project remain in this repo under their original names (the audit log preserves the mk name for those releases verbatim).