feat(extensions): make extensions work with `base`
Metadata
Current evaluation
Merged a feature update that enables extensions to work with the base configuration and relaxes associated validation rules. Authored by lengau to address CHARMCRAFT-703.
Suggested action: —
No scores available.
Issue body
Also relaxes the validation.
CHARMCRAFT-703
Describe your changes.
---
- [x] I've followed the [contribution guidelines](https://github.com/canonical/charmcraft/blob/main/CONTRIBUTING.md).
- [x] I've signed the [CLA](http://www.ubuntu.com/legal/contributors/).
- [x] I've successfully run `make lint && make test`.
- [x] I've added or updated any relevant documentation.
- [ ] In documents I changed, I [added a meta description](https://canonical-starflow.readthedocs-hosted.com/how-to/add-a-page-meta-description/) if one was missing.
- [ ] I've updated the relevant release notes.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged a feature update that enables extensions to work with the base configuration and relaxes associated validation rules. Authored by lengau to address CHARMCRAFT-703. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged. The change enables extensions to work with the base configuration and relaxes validation rules, addressing CHARMCRAFT-703. Approved by maintainers. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1248 feat(extensions): add basic support | charmcraft | merged | Merged to resolve issue #1238, adding basic extension support. Approved by two reviewers, apply_extensions now runs in unmarshal after base expansion to support unified charmcraft.yaml formats, requiring double base expansion if extensions modify bases. (+750/-3 lines, 10 files) |