Upgrade to v2 the `metadata.yaml` generated by `init`
Metadata
Current evaluation
The charmcraft init metadata.yaml format was upgraded to the v2 specification. The maintainer closed the issue as already completed.
Suggested action: —
No scores available.
Issue body
When doing `charmcraft init` the tool leaves a `metadata.yaml` file. We need to upgrade its format to make it compliant with the [v2 specification](https://discourse.charmhub.io/t/charm-metadata-v2/3674).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | The charmcraft init metadata.yaml format was upgraded to the v2 specification. The maintainer closed the issue as already completed. | |
| qwen/qwen3.6-35b-a3b | — | — | Charmcraft init metadata.yaml was already upgraded to v2 specification. Issue closed as implementation was confirmed complete. | |
| qwen/qwen3.6-35b-a3b | — | — | The charmcraft init metadata.yaml format was already updated to comply with the v2 specification. The maintainer closed the issue as the upgrade was completed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | The charmcraft init metadata.yaml format was already upgraded to v2 specification, so the issue was closed as completed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | The charmcraft init metadata.yaml format was upgraded to v2. The maintainer closed the issue directly, confirming the change was already implemented. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1468 replaced metadata.yaml with charmcraft.yaml in integration test templates | charmcraft | closed | Abandoned due to unresolved CLA signature issues. The maintainer confirmed the template update was valid and created a new PR to apply the changes and resolve the check. |