chore: use release backends for cargo tools

[jdx]

Summary

• replace cargo:cargo-insta with aqua:mitsuhiko/insta
• replace cargo:cargo-release with github:crate-ci/cargo-release
• replace cargo:cargo-semver-checks with github:obi1kenobi/cargo-semver-checks
• replace cargo:git-cliff with aqua:orhun/git-cliff
• keep cargo-binstall because cargo:cargo-edit still uses the cargo backend

Validation

• mise install smoke tests for the new GitHub/aqua specs in an isolated mise data dir
• mise -C . ls

---

Note

Low Risk
Dev-environment and lockfile-only changes; no application runtime code, with the same tool versions and CLI entrypoints for existing mise tasks.

Overview
Switches four dev tools in mise.toml from cargo: installs to prebuilt release backends, with a matching mise.lock refresh (per-platform checksums and download URLs).

cargo:cargo-insta, cargo:cargo-release, cargo:cargo-semver-checks, and cargo:git-cliff are removed and replaced by aqua:mitsuhiko/insta, github:crate-ci/cargo-release, github:obi1kenobi/cargo-semver-checks, and aqua:orhun/git-cliff at the same versions where applicable. cargo:cargo-edit and cargo-binstall are unchanged so the remaining cargo-backed tool can still be installed.

Existing mise tasks (snapshots, release, lint:semver) still invoke the same binaries (cargo insta, cargo release, etc.); only how mise fetches them changes.

^{Reviewed by Cursor Bugbot for commit 56ddf41. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Warning

Review limit reached

@jdx, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 68e2f6ab-f1be-4c84-962e-9d4b4e35876a

📥 Commits

Reviewing files that changed from the base of the PR and between 7e05325 and 56ddf41.

⛔ Files ignored due to path filters (1)

• mise.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• mise.toml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Greptile Summary

This PR migrates four developer tool entries in mise.toml from the cargo: compile-from-source backend to prebuilt binary backends (aqua: and github:), eliminating the need to compile those tools locally. Tool versions are unchanged.

• cargo:cargo-insta → aqua:mitsuhiko/insta (v1.48.0)
• cargo:cargo-release → github:crate-ci/cargo-release (v1.1.2)
• cargo:cargo-semver-checks → github:obi1kenobi/cargo-semver-checks (v0.48.0)
• cargo:git-cliff → aqua:orhun/git-cliff (v2.13.1)
• cargo-binstall and cargo:cargo-edit are intentionally kept unchanged as cargo-edit still needs the cargo backend.

Confidence Score: 5/5

Safe to merge — only developer tooling specs are changed, no application or runtime code is affected.

All changes are confined to mise.toml and its generated lock file. The four tool specs switch from compile-from-source cargo backends to prebuilt binary backends while preserving the same tool versions. The lock file includes SHA-256 checksums for every platform, providing integrity verification. No CI workflows, Rust source, or other project files are touched.

No files require special attention.

Important Files Changed

Filename	Overview
mise.toml	Swaps four tool specs from cargo: to aqua: or github: backends; no version changes, only backend source changes
mise.lock	Lock file regenerated with platform-specific checksums and URLs for the four newly-specified backends; old cargo entries removed

_{Reviews (2): Last reviewed commit: "chore(deps): update mise lockfile for re..." | Re-trigger Greptile}