`charmcraft release` doesn't use output text from the store.
Metadata
Current evaluation
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.
Suggested action: needs triage
Reason: The issue is a real bug: ReleaseCommand.run() in charmcraft/application/commands/store.py still builds its output message from parsed_args.resource rather than the store's release response, and Store.release() in charmcraft/store/store.py returns the store's JSON but the command ignores it. No labels, no maintainer comments, no assignee, and no linked PR addressing it, so it has not been triaged. The bug is still present in current code, so it should not be closed as stale or not-a-bug.
Impact:
30
Quick Win:
21.0
Staleness:
75
Complexity:
30
Confidence:
70
Support Request:
10
Issue body
### Bug Description
See: https://matrix.to/#/!LhFxJIPEcCacgdMghH:ubuntu.com/$2wA7g19ZK3W-wrIyLxAB4ZUADQsSRmBTfaQVsIYkn5M
The store commands aren't parsing the data from the store when responding with store info that was pushed
### To Reproduce
Run `charmcraft release` on something with resources. Note that it just returns the resource info provided by the user
https://github.com/canonical/charmcraft/blob/2d43204452b281f1c9d638ac505cb94fa12c1f71/charmcraft/commands/store.py#L762-L777
### Environment
n/a
### charmcraft.yaml
```shell
n/a
```
### Relevant log output
```shell
# uploading the image
charmcraft upload-resource kafka-k8s kafka-image --image=sha256:74e809db37dadf6ad50d5e3420989757c77ba867b466d2e44e2bac68311e4e27
Uploading from local registry.
Image uploaded, new remote digest: sha256:84fc01804541cbff283629f68730915d3649cde5bc4b853b1d347687e7ecb861.
Revision 42 created of resource 'kafka-image' for charm 'kafka-k8s'.
# uploading the charm
charmcraft release kafka-k8s --revision 48 --channel=3/edge/strimzi-oauth --resource=kafka-image:42
Revision 48 of 'kafka-k8s' released to 3/edge/strimzi-oauth (attaching resources: 'kafka-image' r42)
# deploying the charm
juju deploy kafka-k8s --channel 3/edge/oauth-strimzi --revision 48 kafka
Located charm "kafka-k8s" in charm-hub, revision 48
Deploying "kafka" from charm-hub charm "kafka-k8s", revision 48 in channel 3/edge/oauth-strimzi on ubuntu@22.04/stable
# showing resources
juju resources kafka
Resource Supplied by Revision
kafka-image store 41
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
21.0
Staleness:
75
Complexity:
30
Confidence:
70
Support Request:
10
|
needs triage | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
45
Confidence:
80
Support Request:
10
|
needs triage | Bug report stating charmcraft release fails to parse and display resource information from the Charm Store API, showing stale user-provided data instead. Issue lacks labels, assignee, and maintainer comments after over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
45
Confidence:
80
Support Request:
10
|
needs triage | charmcraft release command ignores store response data when reporting resource info, causing revision mismatches. Unlabelled, no maintainer comments, open for ~2.5 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
40
Confidence:
80
Support Request:
5
|
needs triage | Bug where charmcraft release fails to parse and display resource data returned by the store API. Reported by a maintainer with reproduction steps and a code pointer, but remains unlabelled and inactive for over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
80
Complexity:
45
Confidence:
65
Support Request:
10
|
needs triage | charmcraft release fails to parse store responses, echoing back user-provided resource info instead of actual store data. This causes incorrect resource revision reporting. Open, unassigned, no comments, awaiting triage. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #847 Improve the 'release' response when resources are automatically released with the charm | charmcraft | 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. |