[jdx]

https://entire.io/gh/jdx/mise/trails/476

A registry entry that moves to another repo or org within the same backend no longer triggers the "registry now installs it from …" warning, and no longer appears in mise backends switch or mise doctor.

Before, a tool locked or installed on vfox:mise-plugins/vfox-lua was reported as superseded once the registry listed vfox:jdx/vfox-lua:

lua is locked to vfox:mise-plugins/vfox-lua, but the registry now installs it from vfox:jdx/vfox-lua. Run `mise backends switch lua` to switch.

There is nothing for the user to switch: the tool installs the same way from the same kind of backend. Now only a change of backend kind counts (aqua: to github:, asdf: to vfox:, …). A repo or org rename within a kind, such as mise-plugins/* to jdx/* or one aqua: package name to another, is ignored.

The check is shared by the runtime warning, mise backends switch, and mise doctor.

AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: unavailable.

🤖 Generated with Claude Code

---

Note

Low Risk
Diagnostic and switch-detection logic only; install resolution via full() is unchanged. Wrong kind comparison could hide real migrations or show spurious warnings.

Overview
Registry vs. installed backend mismatches now compare backend kind (the prefix before :), not the full backend string.

Adds shared same_backend_kind and wires it into BackendArg::superseded_backend (lock warnings, mise backends switch) and mise doctor backend mismatch checks. Repo/org or package renames within the same kind (e.g. vfox:mise-plugins/... → vfox:jdx/...) no longer count as a switch; cross-kind changes (aqua: → github:, vfox → asdf) still do.

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

Summary by CodeRabbit

• Bug Fixes
  • Backend recommendations now recognize installed backends of the same kind as matches, even when their repository or package identifiers differ.
  • Backend changes across different kinds continue to be identified as mismatches.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository YAML (base), Central YAML (inherited), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: d7a52c8c-7cc9-4bcd-925e-0fd0309a32c9

📥 Commits

Reviewing files that changed from the base of the PR and between 38c4ec6 and 78d870f.

📒 Files selected for processing (3)

• src/args/backend_arg.rs
• src/args/mod.rs
• src/cli/doctor/mod.rs

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 2 remain after this review.

---

📝 Walkthrough

Walkthrough

Backend identifiers with the same kind now match even when their repository or package identifiers differ. The public comparison helper is used by backend supersession checks and doctor mismatch analysis.

Changes

Backend-kind matching

Layer / File(s)	Summary
Define backend-kind comparison src/args/backend_arg.rs, src/args/mod.rs	Add and export same_backend_kind. Tests cover same-kind identifier changes and cross-kind differences.
Use backend-kind comparison src/args/backend_arg.rs, src/cli/doctor/mod.rs	Backend supersession and doctor mismatch checks use backend-kind matching instead of requiring exact identifiers.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 78d87

Registry renames within the same backend kind no longer trigger switch warnings or recommendations. Backend selection and installation remain unchanged, and no actionable merge-blocking risk is evident.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 6 functions across 3 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely states the main change: warn about a backend switch only when the backend kind changes.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

• Fix all pre-merge checks with AI

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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]

Confidence Score: 5/5

[Medium risk] Changes when backend configuration switches trigger warnings.

The PR appears safe to merge and matches its stated behavior.

What we checked:

• Different backend kinds still differ: same_backend_kind requires equal names before the colon. Tests check that Aqua versus GitHub and vfox versus asdf remain different.

Summary

The PR compares backend kinds instead of full source names when deciding whether a backend was replaced.

• Repository and package changes within one kind no longer trigger locked-backend warnings, switch candidates, or doctor warnings.
• Tests cover same-kind source changes and different-kind comparisons.
• No new actionable issues were found. No previous review threads were supplied.

_{Reviews (2) · Last reviewed commit: "fix(backend): only treat a change of bac..."}

[github-actions]

Instruction counts

benchmark	trend	instructions	Δ	wall (min)	Δ
env	▁█▃	27,288,250 → 27,258,210	-0.11%	19.44 → 19.69ms	+1.33%
hook-env	▁█▅	29,252,527 → 29,236,331	-0.06%	20.35 → 20.43ms	+0.43%
ls	▁█▄	30,974,125 → 30,946,490	-0.09%	21.12 → 21.55ms	+2.04%
registry	▅█▁	40,209,235 → 40,124,381	-0.21%	17.79 → 17.89ms	+0.58%
startup	▁█▃	10,885,777 → 10,872,505	-0.12%	12.32 → 12.12ms	-1.67%

No instruction-count regression above 1%.

_{Only instruction counts gate. Wall clock is shown for context — on identical hardware it moves 4-20% run to run.}

_{Measured by tak — instruction-counted CLI benchmarks, stored in this repository's git notes.}

_{78d870f4bbcf vs 38c4ec67cc37 · measured on the runner, not pushed to the history.}