OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
apps-services medium occasional DISPUTE

Fix omarchy-mise-install failing on an attestation error or a deprecated package name

omarchyarchmiseghopencodedesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Confirmed on this workstation (omarchy 4.0.2-1, mise-bin 2026.9.1-1) that pacman -Qo /usr/bin/mise reports mise-bin 2026.9.1-1, that pacman -Si mise-bin puts it in the omarchy repo served from https://pkgs.omarchy.org/stable/$arch, and that omarchy update reaches it, since /usr/bin/omarchy-update calls omarchy-update-system-pkgs, which is pacman -Syu --noconfirm --overwrite '/usr/share/omarchy/*'. So the record's supported-route claim holds. Also confirmed here: mise registry opencode returns aqua:anomalyco/opencode, mise registry gh returns aqua:cli/cli asdf:bartlomiejdanek/asdf-github-cli, /usr/share/omarchy/install/user/mise.sh really does ship omarchy-mise-install gh and omarchy-mise-install opencode as bare names on the aqua backend, and mise settings --all lists aqua.github_attestations true, which is the setting the maintainer gestured at. Three things were wrong. First, the fix said mise self-update "writes over /usr/bin/mise". It does not, because the Omarchy build has already disabled it, and mise --version on this machine prints mise WARN self-update is disabled for this install, update mise the same way you installed it. The record reached the right conclusion from a mechanism that does not happen. Second, the fix and the verify block both treat omarchy-mise-install gh as the command that installs and prints the attestations line. Reading /usr/bin/omarchy-mise-install shows it only writes a shim into ~/.local/bin and prints nothing, and the install plus verification fire on the shim's first run, so mise use -g gh is the real check. Third, the cause said the maintainer "diagnosed both threads the same way" as a stale registry. He did say exactly that in issue 6886, but in issue 6887 he said the opposite, "a transient failure of GitHub's attestations API rather than a packaging or resolution defect on our side", and closed it not planned asking for timestamps. The stale-mise reading of the attestation shape is the reporter's closing comment, not the maintainer's, which changes the first action from "update mise" to "retry". Both issues were re-read in full with comments today, 2026-09-11, and both are closed as not_planned and are issues rather than pull requests. I could not exercise the failure itself: this machine is already on a current mise with a current registry, I have no sudo so omarchy update was never run, and I did not run mise use -g gh or any command that installs, so the attestations-verified line is taken from the threads rather than reproduced. One loose end left flagged rather than guessed: the reporter of 6887 says mise self-update worked for them, which cannot be true of this packaged mise, so their mise was probably not the omarchy repo build or that build did not disable the command in August.

The cause above was rewritten on 2026-09-11 to match this note; the fix was corrected by the audit itself.
RISK

Do not switch a tool's backend to github: and do not set aqua.github_attestations to false to get past this. Either one permanently disables supply-chain verification for that install in order to work around what the maintainer reads as a transient upstream API error, and changing a backend key also orphans the matching entry in ~/.config/mise/config.toml and forces a re-download.

Symptom

Installing a coding agent or CLI tool through Omarchy's mise wrapper fails, in one of two shapes on Omarchy 4.

The attestation check fails, on gh and on any other tool that resolves to an aqua package:


HTTP error: error decoding response body

Or mise resolves a package name that has moved upstream, so the install fetches the wrong thing:


$ mise registry opencode
aqua:sst/opencode

The reporter who chased the first one was on mise 2025.10.19.

Cause

Two different root causes behind two similar-looking failures, and neither one is anything wired wrong in Omarchy.

The deprecated-package-name shape is a stale mise registry. The OpenCode package moved orgs upstream and mise's registry already followed it, so a current mise resolves aqua:anomalyco/opencode while an old one still resolves aqua:sst/opencode. That is the maintainer's own diagnosis in issue 6886, quoted there as "a stale mise registry rather than something wired wrong in Omarchy".

The attestation shape has a different diagnosis. The maintainer read issue 6887 as a transient failure of GitHub's attestations API rather than a resolution or packaging defect, because HTTP error: error decoding response body is the verification call failing and not the package failing to resolve. He closed it as not planned and asked for a repeat with timestamps. The stale-mise explanation for this shape comes from the reporter, who closed the thread saying that moving from mise 2025.10.19 to 2026.8.6 made the attestation step pass and mise use -g gh then installed gh@2.97.0 with "GitHub artifact attestations verified". So for the attestation shape, retry first and update mise second.

The maintainer declined pinning the backend to github:cli/cli or github:anomalyco/opencode in both threads, for two reasons worth knowing before you reach for it yourself. It trades a transient network error for permanently disabled supply-chain verification, and changing the backend key orphans the existing opencode = "latest" entry in ~/.config/mise/config.toml and forces a re-download for everyone.

Fix

**Omarchy 4.** mise here is the pacman package mise-bin, served from Omarchy's own repo rather than from extra, so take a newer mise the supported way:


pacman -Qo /usr/bin/mise        # /usr/bin/mise is owned by mise-bin
pacman -Si mise-bin             # Repository : omarchy
omarchy update                  # omarchy-update-system-pkgs runs pacman -Syu, which covers that repo
mise --version
mise registry opencode          # aqua:anomalyco/opencode on a current registry

Upstream's advice in both threads is mise self-update, and that does not work on Omarchy 4. The package build has already disabled it, so the command refuses instead of overwriting the packaged binary:


mise WARN  self-update is disabled for this install, update mise the same way you installed it

mise self-update --help says the same thing from the other side: "Packagers can disable this command so that mise is updated through the package manager instead." Keep mise self-update for a machine where mise was not installed by a package manager.

For the attestation shape, retry before you update anything, because the maintainer reads it as a transient GitHub API failure. The install and the verification happen when the tool runs, not when the wrapper is created:


mise use -g gh                  # ends with: GitHub artifact attestations verified

omarchy-mise-install gh is not an install step and is not a test. Read /usr/bin/omarchy-mise-install: it only writes a shim to ~/.local/bin/gh and prints nothing on success. The shim runs mise use -g --quiet gh on its first invocation, which is where the attestation check actually fires. Use it to put the stock wrapper back if you replaced it with a pinned backend:


omarchy-mise-install gh         # bare name, aqua backend, as /usr/share/omarchy/install/user/mise.sh ships it
gh --version                    # this first run is what installs and verifies

If the attestation failure turns out to be persistent rather than transient, the maintainer's named lever is a mise setting rather than a rewritten backend. Verification is on by default:


mise settings --all | grep attestations   # aqua.github_attestations  true

**Plain Arch** is the same shape. Update mise through whatever installed it, which for the extra repo package mise means pacman -Syu, then retry.

Verify


pacman -Qo /usr/bin/mise        # owned by mise-bin
mise --version                  # 2026.9.1 or newer
mise registry opencode          # aqua:anomalyco/opencode
mise use -g gh                  # ends with: GitHub artifact attestations verified

omarchy-mise-install gh is not a verification step. It prints nothing on success and only writes ~/.local/bin/gh.

Sources

mise-stale-registry-attestation-install-failure