it's not possible to close a channel for only one architecture
Metadata
Current evaluation
Architecture-specific channel closing remains unimplemented and open: snapcraft close still targets all architectures, while the Store API has no scoped close operation.
Suggested action: keep open
Reason: StoreCloseCommand still accepts only a name and channel, and StoreClientCLI.close sends a channels list without an architecture; related open #1752459 reports that the Store API has no architecture-scoped close operation. This is a maintainer-filed, valid capability request and is neither resolved nor obsolete, so it should remain open while the API and CLI design are pursued.
Evaluated by: mr-cal-bot
Impact:
38
Quick Win:
9
Complexity:
62
Confidence:
90
Actionability:
64
Issue body
This is the signature for the close command:
snapcraft close [OPTIONS] <snap-name> <channel>...
It doesn't have an architecture argument. So if you close a channel, it's closed for all the architectures. That might be ok as a default, but it would be nice to be able to select only one architecture.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
9
Complexity:
62
Confidence:
90
Actionability:
64
|
keep open | Architecture-specific channel closing remains unimplemented and open: snapcraft close still targets all architectures, while the Store API has no scoped close operation. | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
14
Complexity:
40
Confidence:
70
Actionability:
60
|
keep open | Feature request to add architecture-specific channel closing to `snapcraft close`. Currently closes channels for all architectures. Open 8+ years with no activity. | |
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
18
Staleness:
90
Complexity:
40
Confidence:
55
Support Request:
10
|
needs triage | Feature request: snapcraft close command lacks an architecture argument, so closing a channel affects all architectures. No maintainer response, no labels, no comments. Related Launchpad bug #1752459 also open with no activity. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
90
Support Request:
10
|
close stale | Feature request to add architecture filtering to the snapcraft close command. Open for ~9 years with zero maintainer engagement or comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
90
Support Request:
15
|
close stale | Feature request to add architecture-specific channel closing to the snapcraft CLI. Unaddressed for over 8 years with no maintainer interaction or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
30
Confidence:
90
Support Request:
10
|
close stale | Feature request to add architecture-specific channel closing to the snapcraft close CLI command. Issue is over 8 years old with zero maintainer engagement or comments. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Duplicate Of:
snapcraft (launchpad)#1752459
(confidence 95%)
Nearly identical title and scope; the later issue documents the same missing architecture-specific close capability and Store API limitation.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1752459 Not possible to close a channel for only a specific architecture | snapcraft (launchpad) | open | Acknowledged gap: `snapcraft close` (snapcraft/commands/manage.py) accepts only name+channel and posts {"channels":[channel]} to /dev/api/snaps/<id>/close, closing all arches; no arch-scoped close exists and store API lacks it. Workaround: close then reopen other arches. | |
| #6520 feat(store): close a channel for specific architectures | snapcraft | open | Adds --arch flag to snapcraft close to close channels per-architecture. New feature, 5 days old, no review yet, CI mostly passing with one failing security scan. |