The charmcraft.yaml is not longer optional for build command (CRAFT-784).
Metadata
Current evaluation
Merged #680 in commit 7df649fd, making charmcraft.yaml required for builds and enforcing its mandatory type key through the config schema.
Resolution: closed resolved
Reason: PR canonical/charmcraft#680 was merged as commit 7df649fd. It requires charmcraft.yaml for build commands and validates the mandatory type key during config unmarshalling.
Evaluated by: mr-cal-bot
No scores available.
Issue body
A side effect of consolidating the config file is that the `type` key is no longer optional. The config schema reflects that now, so everything is normally enforced during unmarshalling, even if I had to set a default value when loading an "empty config".
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #680 in commit 7df649fd, making charmcraft.yaml required for builds and enforcing its mandatory type key through the config schema. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged #680, requiring charmcraft.yaml for builds and enforcing its mandatory type key during config validation in merge commit 7df649fd. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged #680 in commit 7df649fd, requiring charmcraft.yaml for builds and making its type key mandatory through config validation. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged in canonical/charmcraft#680 via 7df649fd (commit 667041f5), requiring charmcraft.yaml for builds and enforcing its type key through the schema. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #680 as 7df649fd, requiring charmcraft.yaml for builds and enforcing its mandatory type key through the consolidated config schema. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged #680, requiring charmcraft.yaml for builds and enforcing its mandatory type key through the config schema. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged in canonical/charmcraft#680 (7df649fd), making the charmcraft.yaml `type` key mandatory for build and enforcing it through config validation. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged. The type key in charmcraft.yaml is now mandatory for the build command. Config schema validation enforces this during unmarshalling, with a default fallback for empty configs. Approved by two reviewers and passed CI. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged PR making the type key mandatory in charmcraft.yaml for the build command. Schema updates enforce type validation during unmarshalling, with a default value applied to empty configs. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #654 Enforce deprecation DN02: A charmcraft.yaml configuration file is now required | charmcraft | closed | DN02 was enforced by merged PR #680 (7df649fd), making charmcraft.yaml mandatory for builds and requiring its type key. | |
| #1149 command: charmcraft init to use charmcraft.yaml only | charmcraft | merged | Merged in ca4df024: charmcraft init now generates a unified charmcraft.yaml containing metadata, actions, and config, with profile descriptions and an updated URL. |