Sebastian Thiel

Great news! I could reproduce the issue and can do so consistently. Having less packs seems to be the key here, and from what I can tell, this situation will...

With the latest modification, I cannot reproduce the issue anymore even after a thousand runs, where previously it would trigger after less than 50 iterations usually. ``` ❯ hyperfine -m1000...

Gix v0.63 was just released, and it should fix this issue for good :).

Thanks for contributing. > First test and this is already breaking, because `smart-release` doesn't see that the some crates have already been published to a custom registry. I assume only...

The problem is that it won't be able to assure that the proposed crate version is more recent than the latest published one, and thus fail publishing.

Sounds like a can of worms. The version-tags are important for knowing the segments of commits which should contribute to the changelogs by the way.

Thanks a lot for getting the ball rolling on workspace dependency support! I thought that maybe it's worth it to try to create a new journey tests that exercises this...

I don't think given this requirement, there isn't anything less but to publish `gitoxide` itself, and such a publish can come in many different shapes. Impossible to model these. On...

By the way, I tried to publish with this branch but it failed with an issue around invalid manifests being written. `cargo metadata` failed due to that. I am sorry...

Thank you! I think it should be possible to reproduce the issue if the `gitoxide` `main` branch is reset to 9511416a6cd0c571233f958c165329c8705c2498. Then, `cargo smart-release` will do strange things, I think...