chore(mise): remove 13 phantom tools and a no-op [alias] block#437
Merged
Conversation
mise.toml named 13 tools absent from the mise registry (denojs, pip, cargo, go-task, gofmt, isort, git, gnu-sed, gnu-grep, gnu-tar, vitest, pytest, jest), so mise emitted ~25 warning lines per shell entry while installing none of them. The [alias] block was dead: mise's [alias] maps an alias to a TOOL PLUGIN, it does not define tasks, so build/test/lint/fmt never ran. go-task is dropped rather than renamed: the bare name `task` does not resolve either, despite `mise registry` listing it as aqua:go-task/task. Listing is not resolution — verified with `mise ls-remote`. Verified after `mise trust` (an untrusted mise.toml is silently ignored, so zero warnings from an untrusted file proves nothing): 0 warnings and 0 errors attributable to this file. Introduced by sweep2 (2026-07-18); this is one of 56 repos that committed the broken file (417 identical copies existed estate-wide, most only in uncommitted local working trees). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
hyperpolymath
marked this pull request as ready for review
July 21, 2026 17:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
mise.tomlin this repo named 13 tools which do not exist in the mise registry, plusan
[alias]block that never did anything. The result was roughly 25 warning lines onevery shell entry.
Introduced across the estate by
sweep2on 2026-07-18: one file, copied to 427 repos, 419carrying all 13 phantom names. This repo is one of 56 that actually committed the
broken file (most of the 419 copies exist only in uncommitted local working trees, not on
any remote).
Three faults
1. Thirteen names that do not resolve. Removed, grouped by reason:
cargo(rust),gofmt(go),pip(python)vitest,jest,pytest,isortgit,gnu-sed,gnu-grep,gnu-tardenojs→denogo-taskis dropped, not renamed. The bare nametaskdoes not work either:mise registrylists it asaqua:go-task/task, buttask@lateststill fails to resolve.Worth recording — appearing in
mise registryoutput is not sufficient to conclude a nameresolves; check with
mise ls-remote.justis listed instead, matching the estate'sJustfile convention.
2. The
[alias]block never ran. mise's[alias]maps an alias to a tool plugin;it does not define tasks.
build = "cargo build --release || npm run build || go build"was therefore dead, and mise separately warns
[alias]is deprecated in favour of[tool_alias]. Not re-added as[tasks].Verification
Controlled comparison on one machine, one shell:
purely because mise had refused to parse the file —
Config files ... are not trusted.An untrusted
mise.tomlis silently ignored, so absence of warnings is not evidence ofcorrectness unless the file is trusted first. The numbers above were taken after
mise trust.Acceptance criteria
mise trust)[alias]sectiongo-taskis acceptable (nothing in-repo invokestask)mise.tomlshould be doingmore than it currently does — this PR only removes what was broken
Note deliberately not actioned
Every tool is still pinned to
latest, which is not reproducible and sits awkwardly besidethe estate's SHA-pinning doctrine. Changing that is a judgement call per repo, so it is
flagged here rather than made silently.
Model tier
Haiku/Sonnet — one config file, no code paths, mechanical once the registry facts are
established.