Add ability to `charmcraft close` not supported base.
Metadata
Current evaluation
Charmcraft still closes an entire track/risk[/branch], not one base; base-specific closure awaits Store work in snapstore-server#2088469, while close/re-release is a confirmed workaround.
Suggested action: keep open
Reason: The request is valid and maintainer-triaged: @lengou explicitly opened dependent Store work in snapstore-server#2088469. The current CloseCommand still accepts only name and channel and closes the whole channel, so the feature is unresolved; @milos-lukic and the reporter confirmed that closing and re-releasing only the supported base is a working workaround for the secondary question.
Evaluated by: mr-cal-bot
Impact:
55
Quick Win:
10
Complexity:
72
Confidence:
94
Actionability:
68
Issue body
### What needs to get done
Hi,
At the moment users can close [track/]risk[/branch] [only](https://canonical-charmcraft.readthedocs-hosted.com/en/stable/reference/commands/close/).
However one channel/track usually has several bases, some might be deprecated or just garbage.
It is a feature request to close the specific base only.
Example, see the charm https://charmhub.io/data-platform-libs :
```
> charmcraft status data-platform-libs
Track Base Channel Version Revision
latest ubuntu 20.04 (amd64) stable 2 2
candidate ↑ ↑
beta ↑ ↑
edge 9 9
ubuntu 22.04 (amd64) stable 54 54
candidate 81 81
beta ↑ ↑
edge 81 81
```
The base 20.04 is not updated for many years and was the earlier experiments, garbage at the moment.
We should like to hide/remove/close it to avoid users confusing.
Unfortunately, it is not currently possible, we can close the whole track/risk[/branch] only.
Q2: BTW, can I close the whole track `latest` and then push base 22.04 only (to reopen `latest`).
Will 20.04 re-appear in this case?
Tnx!
### Why it needs to get done
See the example above: to clean early experimental bases in the actively supported track.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
55
Quick Win:
10
Complexity:
72
Confidence:
94
Actionability:
68
|
keep open | Charmcraft still closes an entire track/risk[/branch], not one base; base-specific closure awaits Store work in snapstore-server#2088469, while close/re-release is a confirmed workaround. | |
| ~deepseek/deepseek-pro-latest |
Impact:
35
Quick Win:
7
Complexity:
65
Confidence:
70
Actionability:
55
|
keep open | Feature request to close a specific base within a channel via charmcraft close. Maintainer filed store-side dependency; workaround of closing whole track and re-releasing confirmed. | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
12
Complexity:
50
Confidence:
75
Actionability:
60
|
keep open | Feature request to add base-specific closing to `charmcraft close` command. Currently only channel-level closing is supported. Maintainers have engaged; store-side dependency exists. | |
| qwen/qwen3.8-27b |
Impact:
45
Quick Win:
20
Staleness:
55
Complexity:
55
Confidence:
70
Support Request:
15
|
keep open | Feature request to extend `charmcraft close` to close a specific base within a track/risk/branch, not just the whole channel. Q2 about re-appearing bases after close/re-release was answered and confirmed by the reporter. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
78
Complexity:
35
Confidence:
90
Support Request:
5
|
needs triage | Feature request to allow closing specific bases in charmcraft instead of entire tracks. Unlabelled and awaiting maintainer triage after over a year of inactivity. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
40
Confidence:
85
Support Request:
10
|
keep open | Feature request to allow closing specific bases in charmcraft instead of entire tracks. Maintainers acknowledged it, noted a dependency on a store-side change, and answered a usage question. Last activity ~10 months ago. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
70
Complexity:
45
Confidence:
75
Support Request:
10
|
needs triage | Feature request to allow closing specific bases or channels in charmcraft instead of entire tracks. The issue remains unlabelled and unassigned, with recent maintainer comments only addressing a workaround question rather than triaging the feature request. |
Update history
No update history recorded yet.
Related work
-
Blocked By:
snapstore-server#2088469
(confidence 99%)
The maintainer stated that Store support for closing a specific base depends on this request.
-
Related To:
charmcraft#232
(confidence 98%)
That issue implemented the existing whole-channel close command that this request extends.
Related issues
No related issues found above the similarity threshold.