mise-contrib-add-registry

To add a tool to the mise registry, create a TOML file at registry/<name>.toml declaring available backends and a smoke test. This registers the short-name so users can install it via mise use.

When registering a tool in mise, follow the official backend order: aqua, github/gitlab/forgejo, pipx, npm, then go/cargo/dotnet. This selection order maximizes compatibility across different platforms.

A smoke test is required when creating a mise registry entry to validate the tool installation. It ensures the declared backends function correctly and the tool is discoverable before users run mise install.

The correct file format for a mise registry contribution is a TOML file located at registry/<name>.toml. This single-file entry enforces concise description fields, backend declarations, and test commands.

Yes, you can use pipx or npm as backends for a mise registry entry. The contribution workflow supports multiple backends including aqua, github, go, cargo, and dotnet to maximize installation compatibility.

No, adding a short-name tool to mise requires only a single-file registry entry. You create one registry/<name>.toml file to declare backends and a basic test for the contribution workflow.