Improve the 'release' response when resources are automatically released with the charm
Metadata
Current evaluation
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.
Suggested action: keep open
Reason: The issue is a well-scoped, maintainer-authored feature request (labeled 'good first issue') to improve the release command's output message. The external dependency (Charmhub store bug 1987696) was resolved in October 2022, but the client-side enhancement in store.py still only mentions explicitly attached resources, not automatically released ones. The issue remains valid and actionable.
Impact:
20
Quick Win:
14.0
Staleness:
55
Complexity:
30
Confidence:
70
Support Request:
10
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 |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
14.0
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. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
80
Complexity:
15
Confidence:
75
Support Request:
0
|
keep open | Enhance charmcraft release output to list automatically released resources. The required store API fix is complete, and an internal ticket has been created. Labeled good first issue, awaiting implementation. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1979 `charmcraft upload` should allow a user to also release the charm | charmcraft | open | Feature request to add --release flag to charmcraft upload command. The --release flag is already implemented (PR #255), but auto-uploading resources from upstream-image field in charmcraft.yaml remains unimplemented. Last activity Feb 2025. | |
| #320 charmcraft release doesn't pay attention to resources | charmcraft | closed | Superseded by a Charmhub backend validation request. Resource validation for releases is deferred to the server side. A new bug was opened to track the snapstore-server fix. | |
| #259 Support for attaching resources when releasing charms. | charmcraft | merged | Merged after two approvals. Adds support for attaching resources during charm releases, modifying seven files with 188 additions and 26 deletions to update the release workflow. | |
| #2172 docs: update release step with resource details | charmcraft | merged | Merged documentation update adding resource attachment details to the charm release example, resolving issue #2171. Standardizes charm names across the Publish section. Approved by two reviewers, passed CI, and applied with a minimal eight-line change. | |
| #457 Allow including resources when releasing charms directly in the upload command (CRAFT-381). | charmcraft | merged | Merged. Enables including resources when releasing charms via the upload command, fixing issue #456 and CRAFT-381. Approved by two reviewers with 63 additions across three files. Maintainers prioritized CI workflow improvements. | |
| #1313 Make it easier to release charms in CI and in general | charmcraft | open | Feature request to upload and release a charm plus its OCI resources in one command without tracking integer revision IDs. Skopeo integration landed, but upload --resource still requires name:revision format. Maintainers acknowledge it remains applicable and UX is being considered across crafts. | |
| #1435 `charmcraft release` doesn't use output text from the store. | charmcraft | open | charmcraft release command echoes user-provided resource revisions instead of the store's actual response, so output can be misleading (e.g. shows r42 attached while store attached r41). No maintainer response or labels; code path unchanged since the issue was filed. |