`charmcraft release` doesn't use output text from the store.
Metadata
Current evaluation
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.
Suggested action: needs triage
Reason: Current code still discards Store.release's response and builds the resource-attached message from parsed_args.resource; the supplied log claims resource r42 was attached while Juju reports store revision 41. The report and reproduction are concrete, but the issue has no labels, comments, maintainer assessment, or resolving reference, so it still needs triage.
Evaluated by: mr-cal-bot
Impact:
44
Quick Win:
22
Complexity:
41
Confidence:
94
Actionability:
84
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
44
Quick Win:
22
Complexity:
41
Confidence:
94
Actionability:
84
|
needs triage | 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. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
19
Complexity:
20
Confidence:
70
Actionability:
80
|
keep open | charmcraft release command ignores store API response and constructs output message from user-provided arguments instead of parsing actual store confirmation data. | |
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
21
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. |
Update history
No update history recorded yet.
Related work
-
Related To:
charmcraft#320
(confidence 68%)
A related resource-release issue was closed in favor of Charmhub-side validation, which does not demonstrate that this CLI output-reporting defect was fixed.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2865 docs: charmcraft release reference is badly formatted | charmcraft | open | Docs bug report: the published `charmcraft release` command reference shows `charmcraft release [options] <None> <None> <None>` in Usage, plus unformatted channel and resource examples. Untriaged, no maintainer response. | |
| #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. | |
| #1101 add a "version" option on charmcraft release cli | charmcraft | closed | Rejected: Charmhub only obtains a charm’s version from the built artifact, so Charmcraft did not add a release version option; metadata-based versioning remains separate work. | |
| #847 Improve the 'release' response when resources are automatically released with the charm | charmcraft | 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. | |
| #722 Feature request: charmcraft revisions json / yaml output | charmcraft | closed | JSON/YAML output for `charmcraft revisions` was redirected to broader programmatic Store work in canonical/charmcraft#183; no resolving PR was cited. |