build: do not create metafiles when using reactive
Metadata
Current evaluation
Merged changes preventing metafile creation for the reactive framework due to charmcraft format incompatibility. Resolves issue #1150. Approved by one reviewer, passed CI, and modified one file (+6/-3).
Suggested action: —
No scores available.
Issue body
The reactive framework uses an incompatible
variant that creates its own files.
The format defined by charmcraft cannot be used.
Fix: https://github.com/canonical/charmcraft/issues/1150
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged changes preventing metafile creation for the reactive framework due to charmcraft format incompatibility. Resolves issue #1150. Approved by one reviewer, passed CI, and modified one file (+6/-3). | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a fix to prevent metafile creation when using the reactive framework. The reactive variant generates incompatible files that conflict with charmcraft's format, resolving issue #1150. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged to prevent metafile generation when using the reactive framework, resolving issue #1150. The reactive variant produces incompatible file formats that conflict with charmcraft's build process. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1666 fix: only keep metadata.yaml for reactive charms | charmcraft | merged | Merged to fix issue #1654 by restricting metadata.yaml retention to reactive charms only. Approved by two reviewers, passed CI, and modified six files (+101/-5). | |
| #2502 Fix missing build metadata in reactive charm artifacts | charmcraft | open | Adds .build.manifest preservation and charmtool_version to manifest.yaml for reactive charm builds. Fixes #872. Inactive 263 days, 0 reviewer approvals, several CI checks failing (snap-tests, Conventional Commits policy). | |
| #1524 fix(package): don't write a metadata.yaml if it already exists. | charmcraft | merged | Merged a fix preventing overwrites of existing metadata.yaml files. Approved by two reviewers, this change enables reactive charm support in destructive mode as a partial resolution for issue #1488. | |
| #2245 fix(reactive): don't overwrite config.yaml from a reactive charm | charmcraft | merged | Merged following approval by three reviewers. Resolves issue #2194 and CRAFT-4206 by preventing reactive charms from overwriting config.yaml. Changes affect three files with minor code adjustments. | |
| #777 Do not modify the charm's project when packing using the reactive plugin (CRAFT-928). | charmcraft | merged | Merged to resolve issue #693. The change prevents the reactive plugin from modifying the charm's project during packing. Approved by one reviewer with zero unresolved comments. Two files modified, netting a 21-line reduction. |