Maintainers
Operational docs for releasing and packaging llmenv.
- Release process — cutting a version: changelog,
Cargo.tomlbump, tagging, and the release workflow. Read this before touching the version number,CHANGELOG.md, or a release. - Homebrew tap setup — configuring and publishing the Homebrew tap.
Branch strategy​
Feature development happens on main. Each major.minor version gets a
release/X.X.x long-lived branch for bug fixes. Fix in the oldest applicable
branch first, then merge forward — the fix and its CHANGELOG entry propagate
automatically. See release.md for the full policy
and patch-release workflow.
Versioning invariant​
A version exists only once it has been git-tagged. Until then, every change goes
under ## [Unreleased] in
CHANGELOG.md. git tag -l
is the source of truth
source of truth — no tag means no version section and no Cargo.toml bump. Full
details in release.md.
Design docs​
- Engine capabilities
— the two-layer
(neutral + per-engine
native) capability model.