I stumbled across this while evaluating mise for tool installation in GitHub Actions, as I wanted to reason about the use of checksums within mise itself.
The mise.lock in this repository is inconsistent in it's use of checksums, and I wonder how we arrived at this state. Is this a bug, a usage error (that others could make without noticing) or an entirely different phenomenon?
Last commit on that file can be found here: 0a78015#diff-549ea7445facabb03f3ae96a42b1c9b6b0eb3750b77d3ac388cfdb86e63c6db9 clearly showing that checksums have been there before, but haven't been added for the tools that have been newly added.
I stumbled across this while evaluating mise for tool installation in GitHub Actions, as I wanted to reason about the use of checksums within mise itself.
The mise.lock in this repository is inconsistent in it's use of checksums, and I wonder how we arrived at this state. Is this a bug, a usage error (that others could make without noticing) or an entirely different phenomenon?
Last commit on that file can be found here: 0a78015#diff-549ea7445facabb03f3ae96a42b1c9b6b0eb3750b77d3ac388cfdb86e63c6db9 clearly showing that checksums have been there before, but haven't been added for the tools that have been newly added.