Denis Cornehl

I think I found out what's happening

this is the second regression coming from #2467 For normal build errors (= the build was executed, but failed) we never retried. For other errors before build (like when evalutating...

I just deployed the fix https://github.com/rust-lang/docs.rs/pull/2605 . When you do your next bulk release, everything _should_ start working again as it did for a long time, feel free to reopen...

Some first notes before I can dig deeper: first of all: when we have a list of crate names & exact versions, then we can totally trigger a rebuild for...

I think the [crates.io _reverse dependencies_ list](https://crates.io/crates/generic-array/reverse_dependencies) is the right point to start.

Using the crates.io API I generated the list of releases, @newpavlov can you confirm that the list is fine? Then I'll trigger the rebuilds. Releases that depend on any 0.14...

> @syphar Unfortunately, the list captures only [`crypto-common`](https://docs.rs/crypto-common). Crates which define algorithm traits (e.g. [`digest`](https://docs.rs/digest)) use `generic-array` re-exported from `crypto-common`. Finally, implementation crates (e.g. [`sha2`](https://docs.rs/sha2)) implement the traits and thus...

> (but you need to filter pre versions) which? without the build status filter I'm getting 2676 releases, which we _could_ rebuild, but I would prefer having a filter.

coming back to open issues. I can queue rebuilds for any list of (name, version). To safe us some back and forth around the list I would propose you generate...

I queued the rebuilds. Versions that didn't exist: - belt‑hash 0.1.1 - fsb 0.10.4 - md5 0.10.6