QA (public)

Re-release update is update of already released update for missing channels/targets.
Bot can fail to schedule update because of inconsistency between channels/targets and published repos.
In patchinfo can be channels/targets which is bot expecting to be published, but repo will be not published because it was published and released in previous update.
This does not happen often but when it happens then there are no tests scheduled.
In theory tests which run before should cover also this update which is same, just for another channels/targets.
So we can just manually approve the update or add workaround to make bot schedule this update despite the channels/targets and published repo inconsistency.
I would not automate this rare exception, just make possible to manually trigger tests for the update.

Example of such update
https://maintenance.suse.de/request/316566/ First update
https://maintenance.suse.de/request/319913/ Re-release of the first update

Two threads of this issue
https://suse.slack.com/archives/C02CANHLANP/p1705059696456929
https://suse.slack.com/archives/C02D16TCP99/p1707323276471179