Open joshtriplett opened 2 months ago
Would it be possible to get a gix-testtools release based on this?
Also, is there some process that could avoid having gix-testtools get out of sync?
Actually, I don't think I can do that as it will break the ability of cargo smart-release
to perform a release of gitoxide
. Publishes fail if the test-tools use dependencies in the workspace, and using a separate set of crate versions (that also have to be one major version in the past, ideally) was the only workaround I could find. (gix-testtools
seems to be special as it's used as dev-dependency in crates that are also depend on it, it's a cycle.)
I'd also love to not have this special-case, but it will probably need more time than I can invest into cargo smart-release
to find a proper fix for it - it's a complex tool that was rewritten once already, yet is totally under-tested. My hopes are that one day, cargo smart-release
will only be used to set the crate versions update changelogs, while cargo publish
can be used to publish everything in the right order - then it should be possible to remove this special case.
This avoids duplicate dependencies in packages depending on both gix and gix-testtools.