So it's not forgotten I'll write down my findings here.

When we get a Yank change from crates-index-diff, we are running an UPDATE statement on the releases table.

We only add the release to that table after the build is finished, so when the release is still in our build-queue, or in progress, the yank wouldn't do anything.

Since we don't check the number of updated rows for that UPDATE statement, this also never lead to an error.

While we could solve this issue by storing the yank-state in the build-queue too, this could also be solved via solving #1011.