misleading error message on "release" if mandatory arguments are missing
Metadata
Current evaluation
`snapcraft release` now reports missing required arguments or invalid revision types instead of falsely claiming the release command does not exist.
Resolution: closed resolved
Reason: The closing comment by @mr-cal on 2026-02-05 demonstrated that the CLI now identifies required name, revision, and channels arguments and validates the revision type.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Bug Description
When doing `snapcraft release`, if a mandatory argument is missing, the error message will claim that there's no such thing as the `release` command, instead of flagging the missing argument.
### To Reproduce
```bash
snapcraft release <snap> latest/edge # missing the revision
```
### Environment
```bash
$ snapcraft version
snapcraft 7.5.3.post110+git5fbaab14
```
on Jammy.
### snapcraft.yaml
```shell
n/a
```
### Relevant log output
```shell
Usage: snapcraft [OPTIONS] COMMAND [ARGS]...
Try 'snapcraft -h' for help.
Error: No such command 'release'.
```
### Additional context
_No response_
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | `snapcraft release` now reports missing required arguments or invalid revision types instead of falsely claiming the release command does not exist. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed the release command errors: Snapcraft now identifies missing name, revision, and channels, or an invalid revision value, instead of claiming the command does not exist. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed: `snapcraft release` now reports missing required arguments or invalid revision input instead of claiming the command does not exist. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed the misleading release error: the CLI now reports missing required arguments or invalid input types instead of claiming that release does not exist. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed the misleading error message for missing mandatory arguments in the snapcraft release command. The CLI now correctly prompts for required arguments and validates input types instead of claiming the command does not exist. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed. The misleading error claiming the release command does not exist when arguments are missing was resolved. The tool now correctly reports required arguments and validates input values. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed. The release command now correctly validates and reports missing or invalid arguments instead of incorrectly claiming the command does not exist. Updated error handling now requires name, revision, and channels. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed misleading error reporting for snapcraft release when mandatory arguments are missing. The command now correctly displays required arguments and validation errors instead of claiming the command does not exist. |
Update history
No update history recorded yet.
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. | |
| #1999038 "snapcraft release" chokes given an invalid revision value | snapcraft (launchpad) | 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. | |
| #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. | |
| #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. | |
| #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. | |
| #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. |