Repository navigation
BUG: lockfile_mode = "generate" fails when a Packslip release does not support every target #13099
Unanswered
dkarter
asked this question in
Troubleshooting and bug reports
Replies: 1 comment
|
Confirmed—thank you for the precise diagnosis. I reproduced this with the 2026.9.5 release and the I've opened #13102. It converts only Packslip's With the fix, the same install succeeds and the generated lockfile contains the supported Linux, macOS ARM64, and Windows entries while omitting Linux musl and macOS x64. The focused Packslip suite and the repository formatting/all-features check pass. AI-assisted — Tool: Codex; model: OpenAI/unavailable; version: unavailable. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
What happened
I enabled generate mode in mise 2026.9.5:
When I run:
mise tries to generate lock entries for all target platforms. Pitchfork does not publish binaries for Linux musl or macOS x64.
The command fails with errors such as:
It can also fail for macos-x64.
What I expected
Mise should skip platforms that Pitchfork does not support.
A tool should not need to publish binaries for every lockfile target.
Why this matters
One unsupported platform stops the whole install.
This makes generate mode unusable in projects that contain Packslip tools with a limited platform list.
It also prevents mise from writing the otherwise valid lockfile.
Likely cause
Pitchfork resolves through:
packslip:github.com/jdx/pitchforkThe Packslip backend returns
NoHostArtifactwhen no artifact matches a target.Generate mode only skips errors marked as
UnsupportedTarget. It treatsNoHostArtifactas a normal failure and stops.PackslipBackend::resolve_lock_infoshould convertNoHostArtifactinto mise’s typedUnsupportedTargeterror. Other errors, such as ambiguous artifacts or invalid manifests, should remain fatal.related to #13018
All reactions