Lockfile platforms fall back to the wrong architecture when missing

[GeorgeHahn]

I noticed this when locking "github:mitsuhiko/insta" = "1.46.0". That release does not include linux arm64 builds. The linux-arm64 entry is populated with the x86_64 build. That's not unreasonable if the assumption is that users have emulation setup, but I wanted to double check. Is this intentional?

The lockfile entry created is:
"platforms.linux-arm64" = { checksum = "sha256:0b059e5841da950bcb83c9e75ea722ba08c6bdf615b7e3a09f713c680a83931e", url = "https://github.com/mitsuhiko/insta/releases/download/1.46.0/cargo-insta-x86_64-unknown-linux-gnu.tar.xz", url_api = "https://api.github.com/repos/mitsuhiko/insta/releases/assets/335985148"}

I observe this behavior with mise version 2026.1.1 macos-arm64 (2026-01-08). mise doctor reports no issues.

Related to #6115 where mise use displays a similar fallback behavior on macos.

[jdx]

Thanks for reporting this! I've opened a fix in #7672.

The issue was in the asset matching scoring system - architecture mismatches were only penalized -25 points, which wasn't enough to outweigh the +100 OS match bonus. This allowed mise to silently select an x86_64 build when arm64 was requested but unavailable.

The fix increases the architecture mismatch penalty to -150, making it properly disqualifying. With this change, mise will fail with an error listing the available assets instead of installing an incompatible binary.

---

This reply was AI-generated using Claude Code