release command misbehaving
Metadata
Current evaluation
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.
Resolution: closed not a bug
Reason: Maintainer ~sergiusens explained on 2016-08-20 that snapcraft merely passes three bits of data (snap name, revision, channel) to the store, and that tracking/release logic and channel mapping are generated in the store, then marked the task invalid instead of reassigning. The reporter confirmed there was no snapcraft-side fix and he used the web interface instead.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | 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. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed as invalid: Snapcraft only sent the snap name, revision, and channel to the store; channel tracking and release mappings were handled by the store. | |
| stealth/space-bunny-alpha | — | closed stale | The report documents conflicting release results across stable and candidate, but no linked fix or maintainer explanation is available after 3,677 days of inactivity. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. The report regarding the snapcraft release command channel behavior appears abandoned. No fix was applied. | |
| qwen/qwen3.6-35b-a3b | — | — | The snapcraft release command bug was closed without resolution. No comments or fixes were provided, indicating the channel overwrite issue was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. The snapcraft release command incorrectly overwrote channel versions during sequential releases. The report appears abandoned or resolved in a subsequent update. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | The snapcraft release command incorrectly downgraded the stable channel when releasing to candidate. Closed without comments, indicating abandonment. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1621713
(confidence 72%)
Follow-up report 'snapcraft release doesn't match the spec' on the same release command's revision/channel handling; closed as resolved later, showing later real release-command fixes happened separately.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #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. | |
| #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. |