Build failures

[FintanH]

Hey @Byron 👋

Seems like there's some funkiness going on with building some of the gitoxide crates. The build failed here, and I can reproduce it locally by trying to build radicle-link/librad on the xla/seen branch.

Does it seem like the problem is internal to gitoxide rather than something radiclel-link is doing? Let me know if I can help in any way =]

[Byron]

Oh no, so sorry for that. I was quite confident that nothing can break because I used cargo smart-release and it safety-bumped a bunch of crates which should prevent such thing from happening.

Apparently, that wasn't the case or it wasn't enough.

Tomorrow I will dig right into it and submit a PR for a fix.

Looking at the build failures, it does look like cargo tree -v git-hash would report multiple git-hash versions to be pulled in (which is exactly what shouldn't even be possible). Maybe cargo update will already do the trick, but if not… all I would do is to see align all versions once again which might involve upgrading everything to the latest version. It's so strange though, as I would think that all my publishes today where minor upgrades, hence cargo shouldn't pull these in.

[Byron]

I found the issue that might have caused this breakage, see #222.

[Byron]

Will be fixed with radicle-dev/radicle-link#791 .