Repository navigation
Fix mise install --locked in CI - #30
Merged
Merged
Conversation
mise 2026.11.4 made two things hard errors: - htmlq had lockfile entries with no checksum, which --locked now refuses. Ran `mise lock` to record sha256 for every platform. - The github backend rejects unknown options, and `exe` isn't one. Dropped it; the backend finds the `pmtiles` binary in the archive on its own (`mise exec -- pmtiles version` works). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014hjTWqbmj2SD438mQ5pfnw
aao-react-native set min_version to 2026.11.1. Here too, 2026.11.1 writes mise.lock byte for byte the same as 2026.11.4, the version CI installs, so it is a safe floor: an older mise refuses to run rather than rewrite the lock. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014hjTWqbmj2SD438mQ5pfnw
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.
The mise setup step started failing on mise 2026.11.4 (failing run) with two errors:
No lockfile checksum found for htmlq@0.4.0 on platform linux-x64 (--locked mode). The htmlq entries inmise.lockhad download URLs but no checksums. I ranmise lockto add a sha256 for every platform. I also downloaded the linux-x64 file myself and its checksum matched.option 'exe' is not used by the github backend. I droppedexe = "pmtiles"frommise.toml. mise finds thepmtilesprogram in the download without it.This also sets
min_version = "2026.11.1", the same floor as aao-react-native. mise 2026.11.1 writes this repo'smise.lockbyte for byte the same as 2026.11.4, the version CI installs. With the floor, an older mise refuses to run instead of rewriting the lock.Testing
I tested with mise 2026.11.4, the version the failing run used:
mise install --lockedinstalls all 7 tools.mise exec -- pmtiles versionreports 1.31.2. This is the same callbuild-tiles.shmakes.mise exec -- htmlq --versionreports 0.4.0.mise lockunder 2026.11.1 leavesmise.lockunchanged.Not changed
actionlintis deprecated in favour ofjactionlint. This doesn't fail the build.mise.lockstays on lockfile format 1.mise lock --upgradewould move it to format 4, which only changes the version line. 2026.11.1 and 2026.11.4 write that identically too.locked = true, so a plainmise installnever rewrites the lock. CI here already runs--locked, so I left this out.🤖 Generated with Claude Code
https://claude.ai/code/session_014hjTWqbmj2SD438mQ5pfnw