mise: pin mise - #2027
Conversation
|
|
||
| .make/mise_install: | ||
| @mise install -q | ||
| @./scripts/mise.sh install -q |
There was a problem hiding this comment.
What does the local workflow for this look like? Does this update your global version that is installed? Does mise have a way to automatically use this script instead of whatever mise you have installed? Or is that what it is doing, it's just that in the Makefile you have to use the script?
|
Is there a way we could trial this change on a smaller scale before a full |
This generates a bootstrap script for mise. I wish the script
included the commands to generate it:
mise generate bootstrap -V 2026.1.9 > ./scripts/mise
This helps with a few things:
* It allows us to use a pinned version of mise across local & CI.
Currently we pin CI but have no control over the version people are
using locally, and this can introduce issues. For example if we were
to re-introduce lockfiles, we would need everyone using at least
version X.
* It makes "first day on the job" setup easier because the toolchain
now automatically installs itself. No more "how do I get started?"
* It *might* help with some of the Renovate artifact failures we've
seen. At some point we introduced a host-level mise to our Makefile
targets and this broke "make renovate" since it runs in an isolated
environment. Now Renovate should at least be able to bootstrap mise.
fd14c4e to
fb36c04
Compare
|
@blampe thanks for adding the |
|
Held up by https://github.com/pulumi/pulumi-aws/actions/runs/22246530001/job/64361631729?pr=6190 Reshimming mise 20.19.5... added 1 package in 716ms |
3 participants
This generates a bootstrap script for mise. I wish the script included the commands to generate it:
This helps with a few things:
It allows us to use a pinned version of mise across local & CI. Currently we pin CI but have no control over the version people are using locally, and this can introduce issues. For example if we were to re-introduce lockfiles, we would need everyone using at least version X. Or if/when Cory's fix is merged, we'll want to upgrade everyone to use it across the board.
It makes "first day on the job" setup easier because the toolchain now automatically installs itself. No more "how do I get started?"
It might help with some of the Renovate artifact failures we've seen. At some point we introduced a host-level mise to our Makefile targets and this broke "make renovate" since it runs in an isolated environment. Now Renovate should at least be able to bootstrap mise.