chore(release): fix circular dev-dep publish ordering for hyperdb-api/-derive#101
Merged
Merged
Conversation
…/-derive cargo publish verifies ALL dependencies (including dev-deps) against the crates.io index during packaging. This created an unresolvable circular chain for v0.4.0: hyperdb-api (dev: hyperdb-api-derive =0.4.0) → hyperdb-api-derive (optional: hyperdb-compile-check =0.4.0) → hyperdb-compile-check (runtime: hyperdb-api =0.4.0) → hyperdb-api (dev: hyperdb-api-derive =0.4.0) [circular] No ordering of publishes can break this cycle when all three use version pins, because each requires another to already be on crates.io. Fix: remove the version constraint from the two cross-circular dev-deps: - hyperdb-api/[dev-dependencies]: hyperdb-api-derive path-only (no version) - hyperdb-api-derive/[dev-dependencies]: hyperdb-api path-only (no version) Path-only deps are resolved locally; cargo does not check the registry for them during cargo publish. This breaks the circular registry resolution. Also corrects the publish order in release.yml: hyperdb-api-salesforce → hyperdb-api-core → hyperdb-api-derive → hyperdb-api → hyperdb-compile-check → hyperdb-mcp → ...
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.
cargo publish verifies ALL dependencies (including dev-deps) against the crates.io index during packaging. This created an unresolvable circular chain for v0.4.0:
hyperdb-api (dev: hyperdb-api-derive =0.4.0)
→ hyperdb-api-derive (optional: hyperdb-compile-check =0.4.0)
→ hyperdb-compile-check (runtime: hyperdb-api =0.4.0)
→ hyperdb-api (dev: hyperdb-api-derive =0.4.0) [circular]
No ordering of publishes can break this cycle when all three use version pins, because each requires another to already be on crates.io.
Fix: remove the version constraint from the two cross-circular dev-deps:
Path-only deps are resolved locally; cargo does not check the registry for them during cargo publish. This breaks the circular registry resolution.
Also corrects the publish order in release.yml:
hyperdb-api-salesforce → hyperdb-api-core → hyperdb-api-derive
→ hyperdb-api → hyperdb-compile-check → hyperdb-mcp → ...