fix: publishing crates with correct versions #70
Merged
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
When publishing canbench previously, I had to manually change the local dependencies to point to the versions in cargo (e.g. when publishing
canbench-rs
, I need to change the dependency oncanbench-rs-macros
from the local folder to the new version ofcanbench-rs-macros
that I just published). This process is messy and confusing, and is one of the things that wouldn't be intuitive to anyone publishing canbench in the future.Solution
Update Cargo.toml such that, locally, it uses a folder, and when publishing, it uses a specific version. That way, publishing can be seamless and requires no local modifications moving forward.