fix: load metadata from charmcraft.yaml in profile integration tests
Metadata
Current evaluation
Superseded by PR #1468. The change updates integration tests to load metadata from charmcraft.yaml instead of the deprecated metadata.yaml file.
Suggested action: —
No scores available.
Issue body
Since `charmcraft init` doesn't create a `metadata.yaml` file any more, the integration tests need to load the metadata from the `charmcraft.yaml` file, since they typically run from the source folder rather than within a deployed environment.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Superseded by PR #1468. The change updates integration tests to load metadata from charmcraft.yaml instead of the deprecated metadata.yaml file. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by PR #1468. The integration test fix to load metadata from charmcraft.yaml was closed as a duplicate. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by PR #1468. The change updates profile integration tests to load metadata from charmcraft.yaml, replacing the deprecated metadata.yaml file. |
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. | |
| #2498 fix: `charmcraft pack --project-dir` with metadata.yaml | charmcraft | closed | Merged fix for charmcraft pack --project-dir failing with legacy metadata.yaml. Resolved by changing the working directory to the project directory before loading and preprocessing configuration files. Resolves issue #2493. |