unpublish command and revision history for channel
Metadata
Current evaluation
Feature request for `charmcraft revision <charm> --channel` (per-channel release history) and an `unpublish` command. Maintainer agreed it needs Charmhub backend support; neither option exists in code (revisions command has no --channel, no unpublish command).
Suggested action: keep open
Reason: Valid, maintainer-acknowledged feature request: facundobatista replied "This looks like a good idea, but we depend on Charmhub implementing the functionality" and linked Launchpad bug 1996819. Code inspection at HEAD confirms neither piece exists — `ListRevisionsCommand.fill_parser` in charmcraft/application/commands/store.py only adds a positional `name` (no `--channel`), and a repo-wide grep for "unpublish" only matches charmlib "unpublished_libs" code paths, never a CLI command. The request is blocked on an external Charmhub API, not obsoleted, so it should stay open pending that backend work.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
5
Complexity:
55
Confidence:
78
Actionability:
33
|
keep open | Feature request for `charmcraft revision <charm> --channel` (per-channel release history) and an `unpublish` command. Maintainer agreed it needs Charmhub backend support; neither option exists in code (revisions command has no --channel, no unpublish command). | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
5
Complexity:
40
Confidence:
60
Actionability:
30
|
keep open | Feature request for unpublish command and per-channel revision history. Acknowledged by maintainer but depends on Charmhub backend implementing the functionality. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
16
Staleness:
70
Complexity:
55
Confidence:
80
Support Request:
10
|
keep open | Feature request for a per-channel revision history command and an unpublish command to downgrade a channel. Maintainer acknowledged in 2022 but it is blocked on Charmhub (snapstore-server) API support. Still unimplemented; no activity for over a year. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
40
Confidence:
85
Support Request:
15
|
close stale | Feature request for `charmcraft revision` and `unpublish` commands to track channel history and enable downgrades. Blocked by external Charmhub API, inactive for over three years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
15
Confidence:
80
Support Request:
5
|
close stale | Feature request for charmcraft commands to view channel revision history and unpublish revisions. Blocked on upstream Charmhub API support; inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
30
Confidence:
80
Support Request:
10
|
close stale | Feature request for channel revision history and unpublish commands. Blocked by external Charmhub API changes and inactive for over three years. |
Update history
No update history recorded yet.
Related work
-
Blocked By:
snapstore-server#1996819
(confidence 82%)
Launchpad bug 1996819 cited by facundobatista as the Charmhub-side tracking issue this CLI work depends on (backend must expose per-channel revision history/unpublish before charmcraft can implement it).
Related issues
No related issues found above the similarity threshold.