"snapcraft release" chokes given an invalid revision value
Metadata
Current evaluation
Confirmed parser bug: `snapcraft release mysnap fubar` reports "No such command 'release'" instead of a bad-revision error. Reproduced by mr-cal on 7.2.9, labeled craft-1532, still open with no fix.
Suggested action: keep open
Reason: The bug is confirmed and still live: mr-cal commented "Confirmed. I was able to reproduce this with snapcraft 7.2.9," and the tracker lists it open with the craft-1532 label, so it has been triaged and linked rather than ignored. It is a misleading-error defect (user gets "No such command 'release'" instead of a revision error) with a perfect one-line reproducer, so actionability is high; impact is capped because the command does fail safely, just with a confusing message. Confidence is held down because I could not inspect the code — repo tools errored with 'No pinned SHA available' — so I could not locate the swallowed-UsageError code path, and related issue #1664704 notes that "current releases use craft-store," which may move the fix target outside this repo.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
12
Complexity:
45
Confidence:
65
Actionability:
75
|
keep open | Confirmed parser bug: `snapcraft release mysnap fubar` reports "No such command 'release'" instead of a bad-revision error. Reproduced by mr-cal on 7.2.9, labeled craft-1532, still open with no fix. | |
| stealth/space-bunny-alpha |
Impact:
27
Quick Win:
17
Complexity:
31
Confidence:
91
Actionability:
90
|
keep open | Confirmed parser bug: an invalid release revision makes Snapcraft incorrectly claim that the existing release command is unknown; the report remains open and unresolved. | |
| stealth/space-bunny-alpha |
Impact:
25
Quick Win:
13
Complexity:
35
Confidence:
88
Actionability:
82
|
needs triage | An invalid revision makes snapcraft release incorrectly report that the release command does not exist. The command remains implemented with integer revision parsing, but this report has no maintainer response or identified regression test. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
10
Quick Win:
8
Staleness:
95
Complexity:
15
Confidence:
70
Support Request:
20
|
close stale | Issue about confusing error when 'snapcraft release' receives invalid revision. Stale for 1366 days with no maintainer response. The release command appears to have been removed or deprecated. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
10
Confidence:
85
Support Request:
70
|
close stale | User reports snapcraft release fails with No such command release when passing an invalid revision. Issue is 3.6 years old with no maintainer interaction or comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | snapcraft release command fails with invalid revision, showing generic error instead of specific feedback. Issue is over 3 years old with no activity. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
90
Support Request:
20
|
close stale | Report of snapcraft release command failing with an unhelpful error message when given invalid arguments. Issue is over 3.5 years old with no maintainer interaction or updates. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Duplicate Of:
snapcraft (launchpad)#2059787
(confidence 85%)
Near-identical report: 'inaccurate error output in snapcraft release if given invalid revision' with the same 'No such command release' symptom; also open and untriaged.
-
Related To:
snapcraft (launchpad)#1604810
(confidence 70%)
Same class of defect: misleading error when releasing a nonexistent revision; maintainer-confirmed but awaiting store-specific clarification.
-
Related To:
snapcraft (launchpad)#1664704
(confidence 65%)
Misleading release error for a nonexistent revision; its summary notes the obsolete code path was removed in commit ffb164b7a and current releases use craft-store, hinting the fix target moved.
-
Related To:
canonical/craft-parts#1532
(confidence 50%)
Inferred solely from this issue's 'craft-1532' label, indicating parallel tracking on the craft-parts side; not verified against a tracker lookup.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2059787 inaccurate error output in snapcraft release if given invalid revision | snapcraft (launchpad) | open | Valid CLI parsing bug: an invalid revision makes snapcraft release claim the release command does not exist; current code still uses type=int, and an exact duplicate remains open. | |
| #1664704 snapcraft release gives misleading error when revision does not exist | snapcraft (launchpad) | open | The legacy snapcraft release error wrongly advised registering an already-registered snap; that obsolete code path was removed in ffb164b7a, and current releases use craft-store. | |
| #4401 misleading error message on "release" if mandatory arguments are missing | snapcraft | closed | `snapcraft release` now reports missing required arguments or invalid revision types instead of falsely claiming the release command does not exist. | |
| #1604810 try to snapcraft release an unexisting revision shows the wrong error | snapcraft (launchpad) | open | Maintainer-confirmed misleading error when releasing a nonexistent revision; store-specific behavior still needs clarification before implementation. | |
| #1615215 release command misbehaving | snapcraft (launchpad) | closed | Closed as invalid by maintainer sergiusens: 'snapcraft release' only sends snap-name, revision and channel to the store; channel tracking and release maps are store-side, so the reported behaviour was not a snapcraft bug. | |
| #1604815 The error when trying to release a revision that's not a integer is ugly | snapcraft (launchpad) | closed | Invalid release revisions now produce a formatted user-facing StoreReleaseError; the fix merged in canonical/snapcraft#1599 (c7adb25f7) and shipped in Snapcraft 2.35. |