Comment 3 for bug 1684529

I just want to add: not only is that single snap not released, but _every snap that is pushed after it_ loses the release intent as well. The store hiccuped on the first of like 10 snaps pushed from my CI today, showing a "scan error." Not only did that hold up the automated review of every following snap requiring manual intervention, but the release intent of every other snap pushed was lost. In many cases (since versions don't need to change) it's impossible to determine which release should go to which channel using only version and revision, requiring someone to take _further_ manual interaction to spin up new builds from CI, new uploads, and new releases.