Manage tool versions for local development #184
Assignees
Comments
mitchnielsen
added a commit
that referenced
this issue
May 31, 2024
Manages the tool versions used for development by adding .mise.toml and pinning the tool versions there. This will help keep the tool versions aligned between developer machines (and potentially CI in the future). https://mise.jdx.dev Closes #184
mitchnielsen
added a commit
that referenced
this issue
May 31, 2024
Manages the tool versions used for development by adding .mise.toml and pinning the tool versions there. This will help keep the tool versions aligned between developer machines (and potentially CI in the future). https://mise.jdx.dev Closes #184
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As we saw in #180 (comment), tool versions being different on each developer's machine can lead to problems. It's helpful to manage these tool versions so developers are on the same page.
There are a couple tools that can help with this:
asdfthat drops the slow "shim" approach, and offers some other benefitsLet's try to manage the tool versions for this project and see if we find it helpful in this case. If so, we could consider doing the same for some of our other projects (where it makes sense).
Note to self for future me:
misesupports GitHub CI Actions, which would help us use the same tool versions in CI as we use locally.The text was updated successfully, but these errors were encountered: