← Back to issue list

How to determine what resource revision is associated with a charm revision

View original Github issue

Metadata

Project
charmcraft
Number
#361
Type
issue
State
closed
Author
mthaddon
Labels
—
Created
Updated
Closed

Current evaluation

Closed by author who self-resolved the issue. The charmcraft status command already provides the mapping between charm and resource revisions, requiring no code changes.

Suggested action: —

No scores available.

Issue body

`charmcraft revisions` includes versions of charms uploaded and released, and `charmcraft resource-revisions` includes details of resources uploaded and released, but I can't see a way to determine which resource revision is associated with a particular charm version. Am I missing something?

Evaluation history

Date Model Scores Action Summary
qwen3.6-35b-a3b-mtp-q6 — — Closed by author who self-resolved the issue. The charmcraft status command already provides the mapping between charm and resource revisions, requiring no code changes.
qwen/qwen3.6-35b-a3b — — The author closed the issue after discovering that the charmcraft status command already links charm and resource revisions.
qwen/qwen3.6-35b-a3b — — Resolved by author. The charmcraft status command displays the association between charm and resource revisions. No code changes were required.
qwen3.6-35b-a3b-mtp-q6 — — Self-resolved. The author discovered charmcraft status provides charm-resource revision mappings. Issue closed without code changes or feature implementation.
qwen3.6-35b-a3b-mtp-q6 — — Author self-resolved the issue after discovering that charmcraft status displays the association between charm and resource revisions. Closed without code changes.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#679 Charmcraft should allow resource revisions == 0 when specifying uploads charmcraft closed Closed without resolution or implementation. The request to allow resource revision 0 in charmcraft release commands received no discussion or linked pull requests.
71%