# Mint

> Mint is a Go CLI and GitHub Action for source versioning, immutable artifacts, reviewed environment releases, and verified recovery.

Mint supports arbitrary named environments; production is optional. Your project owns build/deployment adapters and infrastructure. Source tags, verified deployment, and live observations are separate evidence.

## Guides

- [Overview](https://jamesonstone.github.io/mint/index.md): Mint gives every release a clear path from source to artifact to environment. Build once, review an exact selection, and keep evidence of what actually ran.
- [How Mint works](https://jamesonstone.github.io/mint/how-it-works.md): Mint separates release intent from the evidence that makes it safe to act on that intent. Its state lives with your repository and trusted GitHub Actions runs.
- [Integrate Mint](https://jamesonstone.github.io/mint/integration.md): Start with the smallest release model your repository needs. Add environment control when you need reviewed promotion, verified history, or recovery across environments.
- [Environments & sandboxes](https://jamesonstone.github.io/mint/environments.md): Mint models environments by policy, not by a fixed development → staging → production ladder. A repository can contain only sandboxes, several shared test environments, local workspaces, or any project-owned combination.
- [Semantic versioning](https://jamesonstone.github.io/mint/versioning.md): Mint uses strict release tags in the form `vMAJOR.MINOR.PATCH`, such as `v2.4.1`. Prerelease and build-metadata tags are not strict release tags for Mint's resolver or selection commands.
- [CHANGELOG integration](https://jamesonstone.github.io/mint/changelog.md): Mint generates linked Markdown release notes from Git commit history. Good Conventional Commit subjects make both version decisions and changelog entries understandable.
- [Release PRs](https://jamesonstone.github.io/mint/release-prs.md): A Release PR is the review surface for an exact artifact selection and runtime configuration. It is distinct from a source PR: it approves deployment of an already built candidate.
- [Rollback & hotfix](https://jamesonstone.github.io/mint/recovery.md): Prefer roll-forward when practical: correct or revert source, build it, and release a new version. Use rollback for retained-artifact recovery and hotfix to isolate a correction from queued default-branch work.

## Optional

- [Complete documentation](https://jamesonstone.github.io/mint/llms-full.txt): All guides in Markdown.
- [Source and releases](https://github.com/jamesonstone/mint): Implementation and published versions.