Improve the 'release' response when resources are automatically released with the charm
Metadata
Current evaluation
Enhance charmcraft release output to list resources Charmhub automatically attaches; the backend fix is available, but current output only reports resources passed with --resource.
Suggested action: keep open
Reason: The maintainer reported that the linked Charmhub bug is now fix released, making the requested information available. Current release code discards Store.release's response and builds the message only from --resource arguments, so implementing and testing the automatic-resource response remains a clearly scoped improvement.
Evaluated by: mr-cal-bot
Impact:
30
Quick Win:
16
Complexity:
38
Confidence:
94
Actionability:
85
Issue body
Charmhub will automatically release resources if previous releases had them:
```
$ charmcraft status facundo-snappass-test
Track Base Channel Version Revision Resources
latest ubuntu 20.04 (amd64) stable 1 1 redis-image (r1), snappass-image (r1)
candidate ↑ ↑ ↑
beta ↑ ↑ ↑
edge 7 4 redis-image (r1), snappass-image (r1)
...
$ charmcraft release facundo-snappass-test -r 4 -c stable
Revision 4 of charm 'facundo-snappass-test' released to stable
$ charmcraft status facundo-snappass-test
Track Base Channel Version Revision Resources
latest ubuntu 20.04 (amd64) stable 7 4 redis-image (r1), snappass-image (r1)
candidate ↑ ↑ ↑
beta ↑ ↑ ↑
edge 7 4 redis-image (r1), snappass-image (r1)
...
```
The response in the release command should be enhanced to something like '
Revision 4 of charm 'facundo-snappass-test' released to stable, including resources: redis-image (r1), snappass-image (r1)
Charmhub needs to return this information ([issue](https://bugs.launchpad.net/snapstore-server/+bug/1987696))
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
16
Complexity:
38
Confidence:
94
Actionability:
85
|
keep open | Enhance charmcraft release output to list resources Charmhub automatically attaches; the backend fix is available, but current output only reports resources passed with --resource. | |
| ~deepseek/deepseek-pro-latest |
Impact:
35
Quick Win:
20
Complexity:
25
Confidence:
70
Actionability:
75
|
keep open | Release command output omits resources automatically attached by Charmhub; store API now returns this info, so output should list them. Still open, labeled good first issue. | |
| ~deepseek/deepseek-pro-latest |
Impact:
25
Quick Win:
12
Complexity:
30
Confidence:
75
Actionability:
70
|
keep open | Release command output omits resources automatically attached by Charmhub; store API now returns them, so the message should list them. Still open, labeled good first issue. | |
| ~deepseek/deepseek-pro-latest |
Impact:
30
Quick Win:
19
Complexity:
25
Confidence:
85
Actionability:
85
|
keep open | Release command output should list resources automatically released by Charmhub, not only those passed via --resource. Store-side fix is released; charmcraft still ignores the returned resource list. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
17
Complexity:
20
Confidence:
80
Actionability:
70
|
keep open | Enhance 'charmcraft release' message to include automatically released resources. Open for ~4 years, labeled 'good first issue', not yet implemented. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
14
Staleness:
55
Complexity:
30
Confidence:
70
Support Request:
10
|
keep open | Request to enhance the 'charmcraft release' command output to list resources that Charmhub automatically attaches when a revision is released without explicit --resource flags. Store-side fix was released in 2022, but the client-side message enhancement remains unimplemented. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
70
Complexity:
15
Confidence:
85
Support Request:
10
|
keep open | Enhancement request to update charmcraft release output to list automatically released resources. Marked as good first issue, with an internal ticket created and backend dependency resolved. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
88
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Enhancement to update charmcraft release output to list automatically released resources. Backend fix is complete, but CLI implementation remains unaddressed after nearly four years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
75
Support Request:
10
|
keep open | Enhancement request to update charmcraft release output to list automatically released resources. Underlying store dependency was fixed, but implementation remains pending. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapstore-server#1987696
(confidence 99%)
The issue links this backend bug, and the maintainer commented that it was marked fix released.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #457 Allow including resources when releasing charms directly in the upload command (CRAFT-381). | charmcraft | merged | Merged PR #457 (b5d735b4), adding --resource support to upload --release and fixing #456; the fix shipped in Charmcraft 1.1.2. | |
| #2171 "Publish a charm to Charmhub" should include an example with your first resource. | charmcraft | closed | Documentation now shows how to attach a resource revision when releasing a charm; fixed by merged PR canonical/charmcraft#2172 (commit df9125d6). | |
| #1435 `charmcraft release` doesn't use output text from the store. | charmcraft | open | charmcraft release ignores Charmhub's response and prints resource details from CLI arguments, potentially reporting a different revision than was attached; no fix or maintainer response is recorded. | |
| #2172 docs: update release step with resource details | charmcraft | merged | Merged documentation PR #2172 in commit df9125d6, adding resource-attachment details and consistent charm naming to the Charmhub release example; it fixes #2171. | |
| #262 Support resources when showing charm status. | charmcraft | merged | Merged PR #262 (commit eb11a844) added resource revision details to charm status output, completing resource support tracked in #176. | |
| #1313 Make it easier to release charms in CI and in general | charmcraft | open | Single-command charm upload and release with OCI resources remains unimplemented; upload accepts only existing resource revisions, so users must upload resources first and track returned IDs. | |
| #126 Add a "--release" option to the "upload" command | charmcraft | closed | Implemented charmcraft upload --release in canonical/charmcraft#255 (merge 9064a3f3, feature bc06a62a); #457 added resource support and shipped in Charmcraft 1.1.2. | |
| #320 charmcraft release doesn't pay attention to resources | charmcraft | closed | Closed 2021-11-17 without a charmcraft fix: maintainers agreed resource validation belongs in Charmhub, tracking it as Launchpad snapstore-server bug #1951271. |