Skip to content

ci: complete mise.lock, pin mise and install with --locked - #439

Merged
ThomasK33 merged 4 commits into
mainfrom
ci/complete-mise-lock
Nov 9, 2026
Merged

ThomasK33 merged 4 commits into
mainfrom
ci/complete-mise-lock

Conversation

@ThomasK33

@ThomasK33 ThomasK33 commented Nov 9, 2026 •

Copy link
Copy Markdown
Member

Why

CI's "Set up mise" step failed twice today on two PRs (the 0.4.0 release PR, run 42637745893, and #438, run 42650046753), each time after three timeouts downloading https://www.lua.org/ftp/lua-5.5.0.tar.gz. All 15 tools were already restored from the mise cache. The download happened anyway because mise.lock was incomplete: with lockfile = true, mise install writes every entry that mise lock would write, and it downloads the tool to compute a missing checksum.

What

  • mise.lock: the output of mise lock -p linux-x64,macos-arm64 on main. It adds the Lua checksum for both platforms, the github:ThomasK33/reviewfixer entries (the reviewfix task's tool), and LuaJIT's conda packages for linux-x64. The Lua checksum sha256:57ccc32b… matches the hash that www.lua.org/ftp/ publishes and the hash of the downloaded tarball.
  • unit-tests: "Set up mise" now runs mise install --locked (install_args). It installs only tools listed in mise.lock, never rewrites it, and fails at once when a tool is missing from it, instead of downloading lock data on every run. Lua still downloads from www.lua.org on a cold cache, because the vfox plugin supplies that URL.
  • release-please.yaml and release-notes.yaml: their mise setup installs with --locked too (--locked node communique, --locked communique). Runs 42640921895 and 42649849602 show both release jobs checking all 32 lock targets, Lua included.
  • All three mise setups pin mise 2026.11.5 with the sha256 of its linux-x64 binary (7a5b051d…). The --locked rules changed in 2026.11.0, and CI otherwise takes each new mise release on the day it ships. The release tarballs match the release's SHASUMS256.txt, and the .tar.gz and .tar.zst archives hold the same binary.
  • mise.toml: the [settings] comment now says to keep the lock complete and why, and that the vfox backend (Lua, Neovim) records a checksum without comparing the download with it.

Testing

  • With main's mise.lock, MISE_LOG_LEVEL=debug mise install (all tools installed) logged 10 www.lua.org references and rewrote mise.lock (41 added lines). With this mise.lock, the same command logged 0 and left the file byte-identical, twice.
  • With only the repo's config (global and system mise configs disabled), mise install --locked exited 0 with 0 www.lua.org references on both main's and this mise.lock, and rewrote neither.
  • With the pinned mise 2026.11.5, an empty data folder and no global config: mise install --locked node communique and mise install --locked communique both exited 0. With communique's checksum removed from the lock, --locked failed at once with "No lockfile checksum found".
  • actionlint and zizmor on all workflows: no findings.
  • mise run all: treefmt 0 changed, luacheck 0 warnings / 0 errors, 1062 successes / 0 failures / 0 errors / 7 pending.

The first CI run on this PR misses the mise cache (the key follows the lockfile), so it downloads every tool once.


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high

… run

mise.lock lacked the Lua checksum, the reviewfixer task tool and LuaJIT's conda packages, so every `mise install` in
CI wrote those entries again and downloaded lua-5.5.0.tar.gz from www.lua.org to do it, even with all tools cached. A
slow lua.org then failed "Set up mise". A new unit-tests step fails when `mise install` changes mise.lock.

_Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high_
@ThomasK33

Copy link
Copy Markdown
Member Author

@codex review

@ThomasK33

Copy link
Copy Markdown
Member Author

@codex security review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-09T16:58:12.102221Z cfabf46 Manual request
🔒 Security Review ✅ Completed 2026-11-09T16:58:40.953876Z cfabf46 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review

Security review completed. No security issues were found in this pull request.

Reviewed commit: 26897257de

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 26897257de

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .github/workflows/test.yml Resolved
…lock afterwards

_Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high_
@ThomasK33

Copy link
Copy Markdown
Member Author

@codex review

@ThomasK33

Copy link
Copy Markdown
Member Author

@codex security review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Hooray!

Reviewed commit: 092189c053

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review

Security review completed. No security issues were found in this pull request.

Reviewed commit: 092189c053

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

_Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high_
@ThomasK33 ThomasK33 changed the title ci: complete mise.lock so mise install stops downloading Lua on every run ci: complete mise.lock, pin mise and install with --locked Nov 9, 2026
@ThomasK33

Copy link
Copy Markdown
Member Author

@codex review

@ThomasK33

Copy link
Copy Markdown
Member Author

@codex security review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 371f281335

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review

Security review completed. No security issues were found in this pull request.

Reviewed commit: 371f281335

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

_Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high_
@ThomasK33

Copy link
Copy Markdown
Member Author

@codex review

@ThomasK33

Copy link
Copy Markdown
Member Author

@codex security review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Hooray!

Reviewed commit: cfabf46290

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review

Security review completed. No security issues were found in this pull request.

Reviewed commit: cfabf46290

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@ThomasK33
ThomasK33 added this pull request to the merge queue Nov 9, 2026
Merged via the queue into main with commit d721d72 Nov 9, 2026
7 checks passed
@ThomasK33
ThomasK33 deleted the ci/complete-mise-lock branch November 9, 2026 17:02
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