config: make metadata.yaml file optional
Metadata
Current evaluation
Closed unmerged and superseded by #1126, merged as 044b94f8 to support actions, config, and metadata directly in charmcraft.yaml when separate YAML files are absent.
Resolution: closed superseded
Reason: PR #1122 was closed without merging. PR #1126 subsequently implemented the feature and was merged in commit 044b94f8.
Evaluated by: mr-cal-bot
No scores available.
Issue body
This is a broken commit that will not work for some charms.
Following tasks should fix it when finished.
This PR needs https://github.com/canonical/charmcraft/pull/1121
CRAFT-1747
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Closed unmerged and superseded by #1126, merged as 044b94f8 to support actions, config, and metadata directly in charmcraft.yaml when separate YAML files are absent. | |
| stealth/space-bunny-alpha | — | closed superseded | Closed unmerged; PR #1126 superseded it in commit 044b94f8, allowing metadata in charmcraft.yaml so metadata.yaml is optional. | |
| stealth/space-bunny-alpha | — | closed superseded | PR #1122 was closed unmerged; #1126 (044b94f8) later implemented optional metadata via charmcraft.yaml, addressing CRAFT-1747. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without merging. The author marked the commit as broken and dependent on another PR, indicating the changes were abandoned pending further fixes. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as abandoned. The commit to make metadata.yaml optional was broken and depended on PR #1121. No merge or subsequent fix was applied. |
Update history
No update history recorded yet.
Related work
-
Superseded By:
canonical/charmcraft#1126
(confidence 100%)
Merged replacement adding actions, config, and metadata support directly in charmcraft.yaml.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1126 Allow use actions/config/metadata in charmcraft.yaml | charmcraft | merged | Merged in canonical/charmcraft#1126 (044b94f8), adding inline actions, config, and ST087-compliant metadata support when standalone YAML files are absent. | |
| #1468 replaced metadata.yaml with charmcraft.yaml in integration test templates | charmcraft | closed | #1468 was closed as superseded after CLA/signature blockers; PR #1540 merged the equivalent metadata.yaml-to-charmcraft.yaml integration-template update in commit f3f82031. | |
| #1666 fix: only keep metadata.yaml for reactive charms | charmcraft | merged | Merged #1666 (b2b127e6), retaining metadata.yaml only for reactive charms so non-reactive repacks no longer carry stale integration metadata; fixes #1654. | |
| #1114 config: support use actions in charmcraft.yaml | charmcraft | merged | Merged #1114 as commit 201b40f6, enabling actions in charmcraft.yaml and refactoring configuration models to avoid circular imports. | |
| #644 Request: be able to specify the location of metadata.yaml (and the rest of the charm code) | charmcraft | closed | Resolved in Charmcraft 3.0 by merged PR canonical/charmcraft#1524 (commit 9988b7db), preserving metadata.yaml generated by the charm tool for reactive charms. |