Skip to content

Conversation

@zhangfengcdt
Copy link
Member

This PR resolves the cargo publish error where internal path dependencies were missing version specifications, which is required by cargo when publishing to crates.io.

Changes

  • Added all internal crate dependencies to [workspace.dependencies] in root Cargo.toml with explicit version 0.2.0 and path specifications
  • Updated all crate manifests to use { workspace = true } instead of { path = "..." } for internal dependencies
  • Added workspace dependencies for both Rust crates and C wrapper crates:

This change ensures that when publishing crates to crates.io, all internal dependencies have proper version requirements specified. The path specifications are maintained in the workspace, so local development continues to work as before, but published versions will correctly reference the version from crates.io.

Testing

  • Verified cargo check --workspace --exclude sedonadb passes
  • Verified key crates build successfully: sedona-geoarrow-c, sedona-expr, sedona-functions, sedona

@zhangfengcdt zhangfengcdt changed the title Fix cargo publish error by adding workspace dependencies with versions bugfix: cargo publish error by adding workspace dependencies with versions Nov 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant