bugfix: cargo publish error by adding workspace dependencies with versions #323
+127
−105
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.
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
[workspace.dependencies]in rootCargo.tomlwith explicit version0.2.0and path specifications{ workspace = true }instead of{ path = "..." }for internal dependenciesThis 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
cargo check --workspace --exclude sedonadbpasses