mintRelease with confidence.
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.
One artifact. Any environment.
Mint is a Go CLI and GitHub Action for release state. It versions source, records trusted immutable builds, coordinates reviewed environment releases, and records verified outcomes. Your application owns the build and deployment adapters.
A sandbox can use the same digest as staging or a customer demo. No environment named production is required. Each environment has its own policy and deployment history; a multi-component application moves as a complete digest bundle.
Start here
- How Mint works: source versions, candidates, frozen intent, and evidence.
- Integrate Mint: choose a release model, add policy, and connect trusted adapters.
- Environments & sandboxes: local versus shared scope, arbitrary names, and promotion prerequisites.
- Semantic versioning: understand what increments a version and what a tag proves.
- CHANGELOG integration: generate linked release notes from Conventional Commits.
- Release PRs: review the selection that will deploy.
- Rollback & hotfix: recover without losing artifact identity or deployment evidence.
Know what is proven
| Evidence | What it means |
|---|---|
| Source tag | A source commit has a version identity. |
| Trusted candidate | A successful build produced an eligible immutable artifact. |
| Approved Release PR | Humans approved an exact selection and runtime configuration. |
| Verified deployment | The adapter verified that exact selection in the environment. |
| Live observation | Timestamped evidence of the runtime at observation time. |
A merge, dispatch, image alias, or GitHub Release alone does not establish live runtime state.
Read with an agent
Use llms.txt for a concise map, llms-full.txt for the complete guides, or the Markdown source link on any page. The site works without JavaScript and loads its fonts locally.