Wrong error when trying to release a devmode snap to stable
Metadata
Current evaluation
Store returns a confusing error when releasing a devmode snap to stable, instead of the actionable UX-documented message suggesting --beta/--edge. Error text originates in the store API, not snapcraft.
Suggested action: close stale
Reason: Not a snapcraft bug: maintainer ~kyrofa noted 'this error comes straight from the store,' and the affected code has left this repo entirely — snapcraft/commands/release.py no longer exists, and AGENTS.md line 21 shows store/release logic now lives in the external craft-store library, whose own guidelines require generic store fixes be made there. No client-side code emits or could intercept the message (grep for 'devmode'/'cannot target'/'Confinement.' finds nothing in snapcraft/ source), and the near-identical sibling launchpad/snapcraft#1602786 closed with no resolving commit. Cosmetic wording-only request that is unactionable here.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
15
Quick Win:
0
Complexity:
80
Confidence:
82
Actionability:
10
|
close stale | Store returns a confusing error when releasing a devmode snap to stable, instead of the actionable UX-documented message suggesting --beta/--edge. Error text originates in the store API, not snapcraft. | |
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
5
Complexity:
65
Confidence:
78
Actionability:
45
|
needs triage | Snapcraft exposes the store's generic devmode-to-stable error instead of the actionable channel and confinement guidance specified by the UX document; the responsible component is unclear. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
11
Complexity:
40
Confidence:
60
Actionability:
60
|
keep open | UX improvement: replace cryptic error message when releasing devmode snaps to stable with a clearer, actionable prompt. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
17
Staleness:
95
Complexity:
15
Confidence:
55
Support Request:
0
|
close stale | Snapcraft displays a technical error ('Revision 2 (devmode) cannot target a stable channel') instead of the UX-specified friendly message ('Cannot release a devmode snap in the stable channel. Try --beta or --edge') when a devmode snap is released to stable. No comments, no labels beyond store/ux, no maintainer response in ~9.5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
95
Support Request:
5
|
close stale | Reports incorrect error message when releasing a devmode snap to stable channel. Expected a user-friendly message directing to beta/edge, but shows a technical revision error. Unaddressed for over 9 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
5
|
close stale | Incorrect error message when releasing a devmode snap to stable channel. Unaddressed for over 9 years with no maintainer comments. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
10
Confidence:
85
Support Request:
5
|
close stale | Incorrect error message when releasing a devmode snap to stable channel. Issue is over 9 years old with no maintainer response or activity. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Blocked By:
canonical/craft-store
(confidence 75%)
AGENTS.md line 21 states store upload/release/track logic moved to the craft-store library, so any fix must be made there rather than in snapcraft.
-
Duplicate Of:
snapcraft (launchpad)#1602786
(confidence 70%)
Same class of 'store returns an unclear/wrong error' issue; closed with no resolving PR or commit, establishing precedent for this store-side UX problem.
Related issues
No related issues found above the similarity threshold.