chore(release): publish hyperdb-compile-check before hyperdb-api-derive#100
Merged
Merged
Conversation
hyperdb-api-derive has an optional dep on hyperdb-compile-check. During `cargo publish` of hyperdb-api-derive, cargo packages the crate and verifies all dependencies (including optional ones) exist on crates.io. Previously hyperdb-compile-check was published *after* hyperdb-api-derive, so the packaging step failed with: no matching package named `hyperdb-compile-check` found location searched: crates.io index Move hyperdb-compile-check to publish after hyperdb-api (which it depends on) but before hyperdb-api-derive (which depends on it). The publish() helper's 'already exists' guard means re-running skips already-published crates safely.
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
1 participant
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.
hyperdb-api-derive has an optional dep on hyperdb-compile-check. During
cargo publishof hyperdb-api-derive, cargo packages the crate and verifies all dependencies (including optional ones) exist on crates.io. Previously hyperdb-compile-check was published after hyperdb-api-derive, so the packaging step failed with:no matching package named
hyperdb-compile-checkfoundlocation searched: crates.io index
Move hyperdb-compile-check to publish after hyperdb-api (which it depends on) but before hyperdb-api-derive (which depends on it). The publish() helper's 'already exists' guard means re-running skips already-published crates safely.