snapcraft close should complain early with one argument
Metadata
Current evaluation
Added early argument validation to the close command to prevent confusing permission errors when users omit the snap name.
Resolution: closed resolved
Reason: The issue was resolved by implementing early argument validation for the close command, as confirmed by maintainer @mr-cal.
Evaluated by: mr-cal-bot
No scores available.
Issue body
I find myself accidentally omitting the snap name quite often with snapcraft and didn't notice my mistake when attempting to close a branch using:
⟫ snapcraft close edge/bump-20
Your account lacks permission to close channels for this snap. Make sure the logged in account has upload permissions on 'edge/bump-20' in series '16'.
snapcraft knows that 'close' needs at least two arguments and additionally it should know that '/' is not a valid character for a snap name. By applying this knowledge, snapcraft could help me realise my typo.
Bonus points if it inspects the current directory for a snapcraft.yaml and suggests the right command to me.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | closed resolved | Added early argument validation to the close command to prevent confusing permission errors when users omit the snap name. | |
| stealth/space-bunny-alpha |
Impact:
34
Quick Win:
28
Complexity:
12
Confidence:
94
Actionability:
94
|
close resolved | Outdated one-argument snapcraft close behavior is resolved: the current CLI requires separate snap-name and channel positionals and fails during parsing before contacting the store; slash validation and YAML hints remain unimplemented. | |
| stealth/space-bunny-alpha |
Impact:
34
Quick Win:
17
Complexity:
38
Confidence:
89
Actionability:
82
|
keep open | A maintainer-confirmed misleading error from a one-argument close call is now prevented by two-position parsing, but snap-name validation and the proposed snapcraft.yaml hint are not evident. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
14
Complexity:
20
Confidence:
60
Actionability:
60
|
keep open | Feature request to add early validation and helpful error messages when 'snapcraft close' is called with missing snap name and channel swapped. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
14
Staleness:
95
Complexity:
30
Confidence:
60
Support Request:
20
|
needs triage | Feature request for snapcraft close to validate arguments early, rejecting a single argument like 'edge/bump-20' and suggesting the correct command from snapcraft.yaml. Unlabeled, zero comments, inactive for nearly 8 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
0
|
close stale | Feature request to improve argument validation and error messaging for the snapcraft close command. Unlabeled, zero comments, inactive for nearly 8 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
10
Confidence:
90
Support Request:
0
|
close stale | Feature request to improve `snapcraft close` argument validation and error messaging. Issue is extremely stale with no maintainer interaction or updates over 8 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Request to improve argument validation and error messaging for the snapcraft close command. Unlabelled, zero maintainer interaction, and inactive for nearly 8 years. |
Update history
| Date | Change |
|---|---|
| closed | |
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1871109 snapcraft should check file creation permissions and warn/error out instead of generating a non-functional snap | snapcraft (launchpad) | closed | Snapcraft now validates the snap skeleton and fails before producing an unusable artifact; merged in canonical/snapcraft#3743 (7c927032d). |