Repository navigation
Let the publishing to crates.io be re-run after a failure - #162
Merged
Merged
Conversation
- When jetdb-cli failed after jetdb was published, a re-run stopped at jetdb with "already exists", leaving jetdb-cli to be published by hand - Ask the crates.io API whether each version is there, skip a crate that is published, and publish the rest - Keep the order, jetdb first, and keep the job failing when publishing or asking crates.io fails Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
CoverageFor 7964236. |
83CF
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.
Summary
cargo publish -p jetdb-clifailed after jetdb was published, re-running the job stopped atcargo publish -p jetdbwith "already exists", so jetdb-cli could only be published by hand.cargo publishon 404, and fails on any other answer or when crates.io cannot be asked. The npm job already works this way.🤖 Generated with Claude Code