Uh oh!
There was an error while loading. Please reload this page.
chore(ci/mise): add lockfile, simplify caching behavior - #5778
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@30052027e6a65d823b9cd0da6f90ca8852a3f6fcPreview package for commit |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:3a96f6f21f
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
## What kind of change does this PR introduce? Upgrades `golangci-lint` to the latest version, per my findings in supabase#5778 (comment) ## What is the current behavior? The build succeeds, but the `golangci-lint` version isn't pointing to an actual commit in the repo: ``` $ golangci-lint --version golangci-lint has version v2.1.6 built with go1.25.11 from (unknown, modified: ?, mod sum: "h1:LXqShFfAGM5BDzEOWD2SL1IzJAgUOqES/HRBsfKjI+w=") on (unknown) ``` ## What is the new behavior? The `golangci-lint` version now points to an actual commit in the repo: ```sh $ golangci-lint --version golangci-lint has version 2.12.2 built with go1.26.2 from c0d3ddc9 on 2026-05-06T11:07:58Z ``` Hopefully no other changes in behavior!
What kind of change does this PR introduce?
Follow-up enhancement to #5761. Adds a
mise.locklockfile and uses that as our cache key (as opposed to building our own).What is the current behavior?
misecache in CI is built by manually grabbing all of the source files and creating our own hash.What is the new behavior?
Uses the
mise.lockfile to create the file hash. Hopefully same caching behavior as before.