How to "unrelease" a charm?
Metadata
Current evaluation
Unreleasing a charm was resolved with `charmcraft close`, added to master/edge so an accidental Charmhub channel release can be removed.
Resolution: closed resolved
Reason: The missing channel-closing capability tracked by charmcraft#232 was implemented in merged PR #530, commit 9310ddaf. A maintainer confirmed the command was available on master and could be used to close the channel.
Evaluated by: mr-cal-bot
No scores available.
Issue body
I've released revision 5 of my charm to `candidate`, but I realized it was a mistake. Is there a way to "unrelease" it?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Unreleasing a charm was resolved with `charmcraft close`, added to master/edge so an accidental Charmhub channel release can be removed. | |
| stealth/space-bunny-alpha | — | closed not a bug | Usage question: no 'unrelease' in Charmhub; maintainer advised re-releasing a prior revision, then closed once `charmcraft close` landed via PR #530 (commit 9310ddaf), fixing #232. | |
| stealth/space-bunny-alpha | — | closed resolved | Question about un-releasing a charm: maintainer explained Charmhub has no 'unrelease', but re-releasing a revision replaces it; the real capability, `charmcraft close <channel>`, was implemented in merged PR #530 (commit 9310ddaf) and shipped on edge. | |
| stealth/space-bunny-alpha | — | closed not a bug | No unrelease action exists; publish another revision to replace the candidate release. Closing the channel was added by merged PR #530 (9310ddaf), available in Charmcraft master/edge. | |
| stealth/space-bunny-alpha | — | closed not a bug | Unreleasing is unsupported; publish another revision to replace the mistaken one. The `charmcraft close` command was available in master/edge to empty a channel. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Charmhub does not support unreleasing revisions. Workaround: release a newer version to overwrite the channel. A charmcraft close command was implemented and released in master/edge to manage channels, resolving the issue. | |
| qwen/qwen3.6-35b-a3b | — | — | Charmhub lacks an unrelease feature. Users can overwrite channels by releasing newer revisions. The related charmcraft close command was implemented and released in the edge channel, resolving the request. | |
| qwen/qwen3.6-35b-a3b | — | — | The unrelease feature was implemented as the close command in charmcraft. It was merged to master and released in the edge channel, enabling channel closure. The issue was closed as resolved. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected as unrelease. Workaround: release newer revisions to overwrite channels. The related charmcraft close command was implemented and released in the edge channel, resolving the request. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#530
(confidence 98%)
Merged PR implementing `charmcraft close` in commit 9310ddaf.
-
Related To:
canonical/charmcraft#232
(confidence 97%)
Implementation issue for closing Charmhub channels, including closing one without a released revision.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #232 Implement `charmcraft close` | charmcraft | closed | Implemented charmcraft close <name> <channel> in merged PR #530 (commit 9310ddaf), using Charmhub's release endpoint with a null revision to close channels. |