Use workspace versions - #249
Merged
Merged
Conversation
Loirooriol
approved these changes
Oct 4, 2025
Loirooriol
left a comment
Loirooriol
left a comment
Collaborator
There was a problem hiding this comment.
Nice! It wasn't much convenient beforehand
This is the version number that most of the Stylo packages follow
Signed-off-by: Nico Burns <nico@nicoburns.com>
nicoburns
force-pushed
the
workspace-versions
branch
from
October 4, 2025 13:19
c2363a0 to
7f249c2
Compare
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
2 participants
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.
These changes are aimed at making version bumps slightly easier as the version numbers will mostly all be in one place.
Changes made:
Cargo.tomland inherited by each package that uses it.This means that the process to bump the "main" version would just be to replace all the instances of that version number in the workspace
Cargo.toml.For the crates which don't follow the "main" version, you would need to update the version in that crate's
Cargo.tomland theworkspace.dependenciessection of the workspaceCargo.toml(which should hopefully be better than having to update each crate that depends on the crate with the updated version).