Caleb Cartwright

> Any ideas how to debug what the actual response data is and why it is breaking? Two common approaches: 1. Look at the Shields source code to determine the...

Thanks for the PR! > It appears to be failing due to some missing credentials. Not sure what needs to be done about that... in CI we funnel the test...

I think it would probably be best to first take the simplest route with the existing problem on the yanked version (first non-yanked version), and then have a follow up...

See also #8666, as it may be worth overhauling the selection logic and encapsulating it somewhere for usage across the relevant classes

Thanks @nyurik. We're a rather smaller maintainer team, so it's basically an "any maintainer, as and when they have time" review strategy vs. any specific person. I haven't had a...

> @calebcartwright thx for the response. I am not too certain I understood it though - shields already uses crate.io-provided "current version" as the default for one of the shields...

As far as the PR itself, yes the review has stalled out but that's not on you and there's not really anything you can do to help. We're essentially down...

Seems reasonable to me to elide any and all yanked versions

Let's hold off on this for a _bit_ as the Tokei maintainer has commented on relevant issues earlier today. In general I'd be in favor of deprecating this service, but...

Linking a prior comment with relevant historical context: https://github.com/badges/shields/issues/4663#issuecomment-588296373