green up CI, test builds using lockfile #70
Merged
Conversation
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
peso
approved these changes
Nov 9, 2025
Collaborator
peso
left a comment
peso
left a comment
There was a problem hiding this comment.
This looks safe enough for me. The build failures can be fixed later.
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.
This is part 2, a follow up to #69 that addresses checking for the lockfile issue raised in #68. It shouldn't matter what order these are merged. CI is currently failing for various reasons, this makes it work but the repo is broken, so if merged first the results will be red. If merged second they should be green. A sample of working runs can be seen here on my fork and here for the other workflow.
Note I can't test the crates.io publish workflow. Yet 😉