audit uses of `as_ref()` and remove those that are ambiguous about gitoxide

[Byron]

Thanks for the heads-up! Indeed, it's not the first time and I can't promise it will be the last one after this one is fixed.

As for bstr, adding new impls for AsRef isn't considered a breaking change (despite the risk), and since I seem to be making that mistake (and so will others), maybe embracing a reactive response is the only way here.

Yanking temporarily gives some time to respond and like in this case, publish a patched release which will be picked up by the most recent gix and the one before.

I will let you know once the fix is available, so the latest version of bstr can be unyanked again.

[BurntSushi]

Thanks sounds good!

[Byron]

It looks like gitoxide-core is also broken (my 'audit' was made by using the latest unreleased local clone so I could compile with what v1.9.2 would be), which means that only the most recent version of gitoxide will install correctly. That fortunately should be fine as this is what most people do and do by default with cargo install gitoxide.

So with git-credentials released as patch and gitoxide-core released as patch, all current users should be safe.

Once CI passes here I will publish the new versions and share them in this issue.

[Byron]

Both gitoxide-core and gix-credentials have been published as patch releases. They should prevent damage downstream as they don't use as_ref() anymore.

[Byron]

Please feel free to close the issue once bstr 1.9.2 is unyanked, and I suppose I will know if it worked by the absence of a flood of new issues 😅,