Manage all CI versions through mise and use binstall (backport #7393)#7409
Merged
Manage all CI versions through mise and use binstall (backport #7393)#7409
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Collaborator
✅ Docs preview has no changesThe preview was not built because there were no changes. Build ID: d79da8a693304fdd8b23adcd |
5fb2e4c to
6f25b8f
Compare
4fec149 to
6e52771
Compare
these both need to be installed on our releasing image
This is now accomplished with `gh`
6e52771 to
586da22
Compare
goto-bus-stop
approved these changes
May 12, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces changes to the CircleCI configuration, replacing various custom installation steps with the use of
misefor tool version management. These changes simplify the CI pipeline, improve maintainability, and ensure consistency across different environments. This allows:cargo binstallwhich mise supportsNuances
cargo install'dxtaskcommand to be invoked via$HOME/.cargo/bin/xtask(where it is installed after we install it from our source) rather than fixing thePATH. It seemed like a huge time savings to not go get that sorted.mise(a package manager) is installed on Windows usingscoop(a package manager that we now install directly), rather thanchocolatey(a package manager that was already installed). It was tempting to use chocolatey since it was installed, but we've had many bad experiences with it at this point. The recommended way to installmiseon Windows is withscoop, so that seemed like the way to go. After this initial bootstrapping, usingmiseall the way seemed like the way to go.This is an automatic backport of pull request Manage all CI versions through mise and use binstall #7393 done by Mergify.