fix(release): unblock crates.io publish for the 0.7 line (0.7.1)#108
Merged
Conversation
crates.io was stuck at 0.6.3: the publish pipeline omitted three crates that aingle_cortex depends on, so 'cargo publish -p aingle_cortex' could never resolve its deps and the whole 0.7.0 publish failed. - Add aingle_ingest (non-optional cortex dep), aingle_wal + aingle_raft (optional 'cluster' deps — crates.io still requires them published) to the publish pipeline in topological order. - Bump the 0.7.0 workspace crates to 0.7.1 for a clean publishable line; internal dep specs stay 'version = "0.7"' (compatible with 0.7.1).
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.
Problem
crates.io is stuck at 0.6.3 while the repo is at 0.7.x. External consumers (and AIngle's strategic goal of being independently adoptable via crates.io) are stranded.
Root cause
The
publishpipeline inrelease.ymlomits 3 crates thataingle_cortexdepends on:aingle_ingest— a non-optional dep (added with the ingest/MCP work).aingle_wal,aingle_raft— optional (clusterfeature) deps; crates.io still requires every dependency published.So
cargo publish -p aingle_cortexcan never resolve its deps → the whole 0.7.0 publish fails → crates.io never advances past 0.6.3.Fix
aingle_walin Phase 1;aingle_ingest+aingle_raftin Phase 2;aingle_cortexstays Phase 3).version = "0.7"(compatible).To release (after merge)
Tag⚠️ crates.io is irreversible — verified the dependency graph + topological order;
v0.7.1on main → the workflow cuts the GitHub release and publishes to crates.io.cargo metadataresolves cleanly.