Schema doesn't offer the bundle type
Metadata
Current evaluation
Closed as not planned by lengau: bundles were being removed from Charmcraft, so adding a "bundle" value to the charmcraft.yaml schema was pointless. Bundle support was then dropped entirely in PR #2320 (2cb4db71) for 4.0.
Resolution: closed not a bug
Reason: Maintainer @lengau closed it 2025-06-10 with "Closing as not planned since we're removing bundles from charmcraft anyway." The feature itself was decommissioned by merged PR #2320 (commit 2cb4db71), which removed bundle support.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Bug Description
The JSON schema for charmcraft.yaml files _accepts_ defining a bundle charm, but it won't indicate to you that it's an option. It only suggests the "charm" type.
### To Reproduce
Run `charmcraft init`. Then, replace the `type` key's value with something that doesn't exist, like `msi`, and check the validator error from your IDE.
### Environment
Any
### charmcraft.yaml
```yaml
name: epic-charm
type: msi
title: Charm Template
summary: A very short one-line summary of the charm.
description: |
I'm a short description.
platforms:
amd64:
parts:
my-part:
plugin: nil
```
### Relevant log output
```shell
Value is not accepted. Valid values: "charm".
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Closed as not planned by lengau: bundles were being removed from Charmcraft, so adding a "bundle" value to the charmcraft.yaml schema was pointless. Bundle support was then dropped entirely in PR #2320 (2cb4db71) for 4.0. | |
| stealth/space-bunny-alpha | — | closed stale | Closed as not planned because bundles were being removed, making bundle schema completion obsolete; later #2320 (2cb4db71) removed bundle support entirely. | |
| stealth/space-bunny-alpha | — | closed stale | Closed as not planned without a schema change; bundle support was removed in #2320 (2cb4db71), making the requested bundle type obsolete. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as not planned. Bundles are being removed from charmcraft, making the schema validation update obsolete. The request is abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as not planned. Bundles are being removed from charmcraft, making the schema validation update unnecessary. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as not planned. The schema validation limitation for the bundle type will not be addressed since bundles are being deprecated and removed from charmcraft. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as not planned. The schema restriction is moot because bundles are being removed from charmcraft entirely, eliminating the need for bundle type support. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as not planned. Bundle support is being removed from charmcraft, so updating the schema to include the bundle type suggestion is unnecessary. |
Update history
No update history recorded yet.
Related work
-
Superseded By:
canonical/charmcraft#2320
(confidence 90%)
PR 'feat!(bundle): remove bundle features' merged as 2cb4db71, removing bundle support from Charmcraft 4.0
-
Related To:
canonical/charmcraft#2227
(confidence 55%)
Earlier commit 8b2a2bb2 'feat: mark bundles as deprecated', the interim step before removal
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2341 Packing a bundle produces a zip that is rejected by charmhub | charmcraft | open | Charmcraft 3.4.6 packs bundles with metadata.yaml instead of bundle.yaml, causing Charmhub rejection. Bundle features removed in Charmcraft 4.0; maintainer requested charmcraft.yaml with no response. |