use mise to install CLI tools / manage their versions - #3495
Conversation
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
Thinking out loud: we added |
valid question of course. How exactly would that look like with the tools we install via mise now? ( I would like to prevent that users have to install everything themselves) |
|
It'd require to have a bigger build system. We'd run command like |
|
but that doesn't solve |
|
No it doesn't. But at least, |
|
For now I hope that this will solve all tool-install issues. Until now it then was super annoying, every dev has to locally install, freeze the version somehow, and in CI the same. Mise seems to solve both sides. |
|
Then sounds good to me. |
misegot recommended to me multiple times over the last months, and having used it on my machine, I like it quite much.It's much easier than the justfile
_ensure_cargo_install, also covers other tools likeactionlint,denoetc.Also, we'll use the same versions, across CI & locally.
One caveat with the way I'm changing the gh workflows: there is no artifact caching any more. Though I don't thing that's a huge issue for npm, deno etc.