chore(release): correct publish order — derive after compile-check#102
Merged
Merged
Conversation
The publish order had hyperdb-api-derive at position 3, before hyperdb-compile-check. But hyperdb-api-derive has an optional dep `hyperdb-compile-check = "=0.4.0"`, and cargo publish resolves optional deps against the live crates.io index during packaging — so it failed with `no matching package named hyperdb-compile-check`. Derived the correct topological order from the version-pinned sibling edges (path-only deps impose no ordering and are not registry-checked): core → salesforce api → core compile-check → api derive → compile-check mcp → api => salesforce → core → api → compile-check → derive → mcp → bootstrap → sea-query Moves `publish hyperdb-api-derive` to after the hyperdb-compile-check block. This is a pure reordering; no Cargo.toml changes. The 'already exists' guard skips the already-published salesforce + core crates on re-run.
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.
The publish order had hyperdb-api-derive at position 3, before hyperdb-compile-check. But hyperdb-api-derive has an optional dep
hyperdb-compile-check = "=0.4.0", and cargo publish resolves optional deps against the live crates.io index during packaging — so it failed withno matching package named hyperdb-compile-check.Derived the correct topological order from the version-pinned sibling edges (path-only deps impose no ordering and are not registry-checked):
core → salesforce
api → core
compile-check → api
derive → compile-check
mcp → api
=> salesforce → core → api → compile-check → derive → mcp → bootstrap → sea-query
Moves
publish hyperdb-api-deriveto after the hyperdb-compile-check block. This is a pure reordering; no Cargo.toml changes. The 'already exists' guard skips the already-published salesforce + core crates on re-run.