bases: allow overriding of compatibility tag
Metadata
Current evaluation
Merged PR #145 added an optional compatibility_tag to BuilddBase, allowing overrides while preserving default behavior (CRAFT-1248).
Resolution: closed resolved
Reason: PR #145 was approved and merged. It added the BuilddBase compatibility tag override and was manually tested across all Craft applications.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [X] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
-----
New optional parameter `compatibility_tag` for `BuilddBase`.
This allows applications to easily override the default compatibility tag without changing the existing behavior.
Manually tested and confirmed on all *craft applications!
(CRAFT-1248)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #145 added an optional compatibility_tag to BuilddBase, allowing overrides while preserving default behavior (CRAFT-1248). | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #145 added BuilddBase.compatibility_tag, allowing applications to override the default compatibility tag without changing existing behavior; landed in commit ebcf7c1. | |
| qwen/qwen3.6-35b-a3b | — | closed resolved | Merged PR adding an optional compatibility_tag parameter to BuilddBase, allowing applications to override the default compatibility tag. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #50 bases: add compatibilty_tag requirement for Base (CRAFT-144) | craft-providers | merged | Merged PR #50, adding the compatibility_tag requirement for Base under CRAFT-144. | |
| #383 bumping the compatibility tag should be more robust | craft-providers | open | Tests still hardcode buildd-base-v7 while production derives it from Base.compatibility_tag, leaving compatibility-tag bumps vulnerable to inconsistent test updates. |