Clarify that each `platform` entry is a 1:1 mapping to output `charm` files
Metadata
Current evaluation
Clarified that each platforms entry produces a separate charm artifact; fixed by merged PR #2794 with regenerated schema JSON and regression coverage.
Resolution: closed resolved
Reason: Merged PR #2794 added the one-to-one platform-to-charm wording to the charmcraft.yaml schema and updated generated-schema regression coverage, resolving the documentation ambiguity.
Evaluated by: mr-cal-bot
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Clarified that each platforms entry produces a separate charm artifact; fixed by merged PR #2794 with regenerated schema JSON and regression coverage. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed via #2794: the charmcraft.yaml schema now clarifies that each platforms entry produces a separate charm artifact, with regenerated schema JSON and regression coverage. | |
| 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. |
Update history
| Date | Change |
|---|---|
| closed |
Related work
-
Likely Fixed By:
canonical/charmcraft#2794
(confidence 99%)
Merged PR directly implements the requested schema clarification and adds regression coverage.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2794 Clarify 1:1 platforms-to-charm mapping in charmcraft.yaml schema | charmcraft | closed | Merged PR #2794 to clarify that each platforms entry produces a separate packed charm, regenerating the schema and adding regression coverage. |