Add a step to CI to validate all the workspace crates are set to the correct versions #443
Conversation
This file contains 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.
One of the hardships we've run into is ensuring all of our crates stay in lockstep, while also keeping them specified locally. To that end, I've written a script in Lune to validate it. It's not very complicated, it just reads through the
Cargo.tomlfiles and iterates through dependencies.I think we should run this in CI so that it'll fail on PRs to up the versions, so I added a step to CI for it.
I am assuming github actions fail if the process exit code isn't
0. This feels like a pretty safe assumption.