Update cargo-dist to v0.28 to access current GitHub runners#857
Merged
Xophmeister merged 2 commits intomainfrom Jan 30, 2025
Merged
Update cargo-dist to v0.28 to access current GitHub runners#857Xophmeister merged 2 commits intomainfrom
cargo-dist to v0.28 to access current GitHub runners#857Xophmeister merged 2 commits intomainfrom
Conversation
* Change to `ubuntu-latest` runners * Use the latest version of cargo-dist * Clean-up some of the steps to make them easier to follow
nbacquey
approved these changes
Jan 30, 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
2 participants
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.
Updates
cargo-distto v0.28 to access the current GitHub runners. Using thelatestrelease doesn't work, because the version needs to be specified inCargo.toml.Note
I have not been able to get prereleases to work, so this is untested. axodotdev/cargo-dist#1707 suggests that bumping the version will resolve the problem we had, but the only way of checking (for now) is to push a
v0.6.0tag -- once this PR is merged -- and hope for the best.If it doesn't work, then I'll delete the
v0.6.0tag as quickly as possible and go back to the drawing board. (See also #856 for tracking a long-term fix to this problem.)