"Publish a charm to Charmhub" should include an example with your first resource.
Metadata
Current evaluation
Documentation now shows how to attach a resource revision when releasing a charm; fixed by merged PR canonical/charmcraft#2172 (commit df9125d6).
Resolution: closed resolved
Reason: PR canonical/charmcraft#2172 merged as commit df9125d6, updating the release example with resource attachment details and explicitly fixing #2171.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
Over here: https://canonical-charmcraft.readthedocs-hosted.com/en/latest/howto/manage-charms/#publish-a-charm-on-charmhub
and probably over here too: https://canonical-charmcraft.readthedocs-hosted.com/en/latest/howto/manage-resources/#publish-a-resource-on-charmhub
We should show how to attach a specific resource revision when releasing a charm.
### Why it needs to get done
This is not clear and causes even charming experts headaches since they need to bootstrap it so infrequently. https://discourse.charmhub.io/t/unable-to-release-charm-to-charmhub-with-optional-resource/16786/7
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Documentation now shows how to attach a resource revision when releasing a charm; fixed by merged PR canonical/charmcraft#2172 (commit df9125d6). | |
| stealth/space-bunny-alpha | — | closed resolved | Documentation now shows how to attach a resource revision during charm release. Fixed by merged PR canonical/charmcraft#2172 (commit df9125d6). | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Documentation updated to show how to attach specific resource revisions when publishing charms. Resolved and merged via pull request #2172. | |
| qwen/qwen3.6-35b-a3b | — | — | Documentation updated to include an example for attaching a resource revision during charm release. Resolved and merged via PR #2172. | |
| qwen/qwen3.6-35b-a3b | — | — | Documentation updates for attaching resource revisions during charm publishing were merged via PR #2172, resolving the request to clarify the release workflow. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved via PR #2172. Documentation was updated to include examples for attaching specific resource revisions during charm release, addressing user confusion and clarifying the workflow. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#2172
(confidence 100%)
Merged documentation PR adding resource revision details to the charm release example.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #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. | |
| #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. | |
| #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. |