Snapcraft upload+release not capturing review error
Metadata
Current evaluation
snapcraft upload --release prints "Revision N created ... and released to ..." even when store review failed ("Status: error while processing"), leaving the revision in no channel. Two examples given; no maintainer response yet.
Suggested action: needs triage
Reason: The issue is unlabelled, unassigned and has no maintainer comment — the only comment is the reporter (farshidtz) adding a second reproduction — so it has not yet been assessed by a maintainer. The report is nonetheless concrete: the CLI logs "Status: error while processing" and still prints "Revision 58 created for 'gemma4' and released to 'latest/edge'", while `snapcraft revisions` shows rev 58 with channel "-" and `snap download --revision=58` fails, corroborated by the store dashboard showing "Rejected. Automated components review found issues". Uncertainty remains because the code path is not pinpointed (the status polling may live in craft-store rather than this repo, which I could not inspect — repo tools returned "No pinned SHA available for project 'snapcraft'") and the trigger is described as "seldom"/rare.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
55
Quick Win:
17
Complexity:
55
Confidence:
70
Actionability:
68
|
needs triage | snapcraft upload --release prints "Revision N created ... and released to ..." even when store review failed ("Status: error while processing"), leaving the revision in no channel. Two examples given; no maintainer response yet. | |
| stealth/space-bunny-alpha |
Impact:
57
Quick Win:
12
Complexity:
67
Confidence:
91
Actionability:
62
|
needs triage | Snapcraft 8/9 upload --release can report a revision as released after a store review error leaves it out of all channels, falsely indicating successful deployment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
70
Quick Win:
42
Staleness:
65
Complexity:
40
Confidence:
80
Support Request:
10
|
needs triage | snapcraft upload --release reports success despite store review failures due to incorrect status handling in notify_upload. Issue is unlabelled and inactive for 74 days. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
45
Complexity:
45
Confidence:
90
Support Request:
10
|
needs triage | Snapcraft CLI reports successful release after upload even when Snap Store automated review fails. Unlabeled and awaiting maintainer triage. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
45
Complexity:
35
Confidence:
90
Support Request:
10
|
needs triage | snapcraft upload --release reports success despite Snap Store automated review failures blocking the release. Unlabelled, awaiting maintainer triage. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft (launchpad)#1743587
(confidence 62%)
"snapcraft push returns non exit zero code if snap requires manual review" — same class of defect: upload/release output does not surface a failed review as an error, so automation treats an unreleased revision as success.
Related issues
No related issues found above the similarity threshold.