Skip to content

ci: use strict lockfile mode and regenerate mise.lock#2975

Open
michaeldwan wants to merge 1 commit intomainfrom
md/regen-lockfile
Open

ci: use strict lockfile mode and regenerate mise.lock#2975
michaeldwan wants to merge 1 commit intomainfrom
md/regen-lockfile

Conversation

@michaeldwan
Copy link
Copy Markdown
Member

mise changed its lockfile serialization format, so mise lock / mise install rewrites mise.lock on every run -- dirtying the tree in CI and locally. This broke the v0.19.0 release build (#2963) and required a git-checkout workaround (#2964).

Regenerate the lockfile with the current mise format and set MISE_LOCKED=1 in all CI workflows. In strict mode, mise reads the lockfile without rewriting it and fails fast if an entry is missing -- so stale lockfiles get caught immediately instead of silently resolved.

The git-checkout workaround in release-build.yaml is no longer needed and is removed.

mise upgraded its lockfile serialization format, causing mise.lock to
be rewritten on every install -- dirtying the tree in CI and locally.

Regenerate the lockfile with the current format and enable MISE_LOCKED=1
in all CI workflows so mise reads the lockfile without rewriting it.
This replaces the git-checkout workaround added in #2964.
@michaeldwan michaeldwan marked this pull request as ready for review April 28, 2026 23:08
@michaeldwan michaeldwan requested a review from a team as a code owner April 28, 2026 23:08
@ask-bonk
Copy link
Copy Markdown
Contributor

ask-bonk Bot commented Apr 28, 2026

All 6 workflows that use mise have been updated with MISE_LOCKED: "1". The homebrew-tap.yaml workflow doesn't use mise, so it correctly wasn't modified.

The PR properly:

  1. Regenerates mise.lock with the new TOML format (expanding inline tables to separate sections)
  2. Adds MISE_LOCKED=1 to all CI workflows that use mise
  3. Removes the git-checkout workaround that was added in ci: ignore mise.lock drift in release build #2964

LGTM

github run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant