Repository navigation
Fix building the release binaries - #170
Merged
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
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.
The release binaries job failed for v0.2.0 (run).
What happened
Only
aarch64-unknown-linux-muslfailed: the other eight targets were cancelled by the matrix's default fail-fast, before they started.The musl targets are built with
cross, which couldn't readCargo.toml:The
rustlsandtracing-subscriberdependencies were written as multi-line inline tables. That's TOML 1.1 syntax, which recent Cargo accepts butcross's TOML parser doesn't.Changes
toml0.8) rejects the releasedCargo.tomland accepts this one.After merging
v0.2.0should attach the seven non-musl binaries. The musl ones will fail again, because the tag has the oldCargo.toml.🤖 Generated with Claude Code