Clarify that each `platform` entry is a 1:1 mapping to output `charm` files
Metadata
Current evaluation
Closed and resolved by updating the charmcraft.yaml schema documentation to clarify that each platform entry generates a separate charm file.
Suggested action: —
No scores available.
Issue body
### What needs to get done
Clarify in the charmcraft.yaml schema that each entry in `platforms` will result in a separate `charm` file on packing.
### Why it needs to get done
We got some questions/confusion about platforms - we should note that each entry specifically becomes its own `charm` file.
https://matrix.to/#/!LhFxJIPEcCacgdMghH:ubuntu.com/$XzGzD_5XLPXzfN2VqSMuoj4-t4C5MH-2nxv7Fh9ZRsY
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed and resolved by updating the charmcraft.yaml schema documentation to clarify that each platform entry generates a separate charm file. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
15
Confidence:
85
Support Request:
10
|
needs triage | Documentation task to clarify that each platforms entry in charmcraft.yaml produces a separate charm file. Currently unlabelled and inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
10
Confidence:
85
Support Request:
0
|
needs triage | Documentation update to clarify that each platforms entry in charmcraft.yaml produces a separate charm file. Unlabelled, zero comments, and inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
10
Confidence:
85
Support Request:
15
|
needs triage | Update charmcraft.yaml schema docs to clarify each platforms entry generates a separate charm file. Issue has zero comments, over 300 days of inactivity, and remains untriaged, awaiting assignment or documentation update. |
Update history
| Date | Change |
|---|---|
| closed |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2794 Clarify 1:1 platforms-to-charm mapping in charmcraft.yaml schema | charmcraft | closed | Merged to clarify the charmcraft.yaml schema, explicitly stating each platforms entry produces a separate charm artifact. Changes include updated schema descriptions, regenerated JSON, and a regression test. | |
| #2174 charmcraft pack outputs different charm filenames depending on base/platform specification in charmcraft.yaml | charmcraft | closed | Closed as working as intended. Maintainers clarified the deprecated bases syntax is retained for backward compatibility, while the newer platforms syntax intentionally allows user-configurable filenames via platform keys. No code changes were implemented. | |
| #2087 Better document how platform names work | charmcraft | open | Docs request to clarify how charmcraft platform names work, especially for multi-base platforms and when a specific name is needed vs. an arbitrary one like 'fred'. The platforms reference now states names are arbitrary and adds naming rules (PR #2590), so it appears addressed. | |
| #2080 docs: add platforms reference and how-to | charmcraft | merged | Merged documentation updates for Charmcraft platforms, bases, and architectures, covering multi-base support. Approved by three reviewers, passed CI checks, and resolved issue #2009. |