Add a jsonschema for charmcraft.yaml in jsonstore
Metadata
Current evaluation
Resolved by merged PR canonical/charmcraft#2183 (commit b4aee1e9), adding automatic charmcraft.yaml schema generation, a checked-in schema, and CI drift and validation checks.
Resolution: closed resolved
Reason: PR #2183, merged as commit b4aee1e9, introduced the generated schema/charmcraft.json, a Makefile regeneration target, and workflow checks for schema drift and validity.
Evaluated by: mr-cal-bot
No scores available.
Issue body
The idea is that editors could retrieve automatically the schema from [the json schema store](https://www.schemastore.org/json/) and validate that charmcraft.yaml makes sense.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Resolved by merged PR canonical/charmcraft#2183 (commit b4aee1e9), adding automatic charmcraft.yaml schema generation, a checked-in schema, and CI drift and validation checks. | |
| stealth/space-bunny-alpha | — | closed resolved | Automatic charmcraft.yaml JSON Schema generation was added in merged PR canonical/charmcraft#2183 (b4aee1e9), with a Makefile regeneration target and CI drift checks. | |
| stealth/space-bunny-alpha | — | closed resolved | JSON Schema support was implemented in merged PR #2183 (b4aee1e9), adding automatic charmcraft.yaml schema generation, a regeneration target, and CI drift checks. | |
| stealth/space-bunny-alpha | — | closed resolved | Schema generation landed in charmcraft PR #2183, commit b4aee1e9, with CI drift checks and a Makefile regeneration target for CRAFT-2806. | |
| stealth/space-bunny-alpha | — | closed resolved | Implemented automatic charmcraft.yaml JSON Schema generation through merged PR #2183 (commit b4aee1e9), completing the work deferred to CRAFT-2806. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed and deferred to internal Jira ticket CRAFT-2806. Maintainers agreed to auto-generate the schema via Pydantic models and submit it to the JSON Schema Store, but the work remains unimplemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed and superseded by internal Jira ticket CRAFT-2806. Maintainers planned to auto-generate the JSON schema from pydantic models, but implementation was not completed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed after maintainers agreed to auto-generate the schema using pydantic models. The request was deferred and tracked internally via Jira ticket CRAFT-2806. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#2183
(confidence 99%)
The merged PR implemented automatic generation and validation of the charmcraft.yaml JSON Schema.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2183 feat: auto-generate charmcraft.yaml json schema | charmcraft | merged | Merged PR #2183 as commit b4aee1e9, adding generated charmcraft.yaml JSON Schema support, CI drift checks, and a Makefile regeneration target. | |
| #471 config: add charm part to documentation (CRAFT-356) | charmcraft | merged | Merged PR #471 via commit e0b18661, documenting the charm part in the configuration schema for CRAFT-356. | |
| #722 Feature request: charmcraft revisions json / yaml output | charmcraft | closed | JSON/YAML output for `charmcraft revisions` was redirected to broader programmatic Store work in canonical/charmcraft#183; no resolving PR was cited. |