← Back to issue list

Add ability to `charmcraft close` not supported base.

View original Github issue

Metadata

Project
charmcraft
Number
#1997
Type
issue
State
open
Author
taurus-forever
Labels
—
Created
Updated
Closed
—

Current evaluation

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.

Suggested action: keep open

Reason: Maintainer @lengau acknowledged the request and filed a dependent store-side bug (snapstore-server bug 2088469) on 2024-11-18, and @milos-lukic answered Q2, which the reporter confirmed. The core feature (per-base close) is still not implemented in CloseCommand (store.py only accepts [track/]risk[/branch]), and depends on the external store API, so it remains a valid, triaged open feature request.

Impact: 45 Quick Win: 20.25 Staleness: 55 Complexity: 55 Confidence: 70 Support Request: 15

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
qwen/qwen3.8-27b
Impact: 45
Quick Win: 20.25
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 65
Complexity: 35
Confidence: 85
Support Request: 10
needs triage Requests charmcraft close to target specific bases instead of entire tracks. Users want to hide deprecated bases. Currently blocked on a store server dependency. Author confirmed a manual workaround. Open and awaiting triage.

Update history

No update history recorded yet.

Related work

  • Blocked By: snapstore-server#2088469 (confidence 75%)

    @lengau stated the store request (bugs.launchpad.net/snapstore-server/+bug/2088469) would be dependent on this feature, indicating the store API must support per-base channel closure first.

Related issues

No related issues found above the similarity threshold.