chore(ci): Bundle crates under the same version_group #1572
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 should solve the diamond problem we had where
hugr-core
get's a breaking release buthugr-passes
only publishes a minor, so cargo automatically updates the latter and we get diverginghugr-core
versions on the dependency tree (so the public APIs break).version_group
defines a grouping of versions, where packages that had changes will all be bumped to the same version.https://release-plz.ieni.dev/docs/config#the-version_group-field
In the previous example, a mayor bump to
hugr-core
will cause a mayor release for bothhugr-passes
andhugr
.On the other hand, a change to
hugr-passes
will not trigger a bump onhugr-core
.An alternative (non-automated) solution to this problem can be done via the
semver-trick
[0,1], but that's a one-off manual solution more useful to avoid problems for external libraries.