Don't allow `build-base` on stable bases
Metadata
Current evaluation
Maintainer task: reject `build-base` on `platforms` charms when `base` is a known stable base, and document proper build-base usage. Still open, tracked as CRAFT-3920.
Suggested action: keep open
Reason: Authored by maintainer lengau with a concrete requirement and a docs reference (PR #2080 comment), and the Jira bot confirms an internal ticket (CRAFT-3920) was filed, so it is triaged and valid. Implementation is a small pydantic validator in PlatformCharm (complementing `_validate_dev_base_needs_build_base`) plus docs, but 'known stable base' still needs a precise definition against const.py's SUPPORTED_BASE_STRINGS/DEVEL_BASE_STRINGS.
Evaluated by: mr-cal-bot
Impact:
40
Quick Win:
18
Complexity:
35
Confidence:
65
Actionability:
70
Issue body
### What needs to get done
On a `platforms` charm, don't allow `build-base` to be set if the `base` is a known stable base.
This needs to include documentation about how to use build-base. See: https://github.com/canonical/charmcraft/pull/2080/files#r1919338151
### Why it needs to get done
The build base is only relevant if we can't build on the given base.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| ~deepseek/deepseek-pro-latest |
Impact:
40
Quick Win:
18
Complexity:
35
Confidence:
65
Actionability:
70
|
keep open | Maintainer task: reject `build-base` on `platforms` charms when `base` is a known stable base, and document proper build-base usage. Still open, tracked as CRAFT-3920. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
14
Complexity:
40
Confidence:
70
Actionability:
80
|
needs triage | Prevent build-base on stable bases with documentation; untriaged - no labels or maintainer response | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
18
Staleness:
70
Complexity:
30
Confidence:
78
Support Request:
10
|
needs triage | Feature request to reject build-base on stable bases in platforms charms, plus documentation. Created by maintainer 776 days ago, no labels, no maintainer response beyond Jira bot. Code still allows build-base on stable bases; not implemented. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
92
Complexity:
50
Confidence:
85
Support Request:
10
|
needs triage | Feature request to restrict build-base on stable bases for platforms charms and update documentation. Unlabelled, inactive for over a year, awaiting maintainer assessment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
30
Confidence:
80
Support Request:
10
|
needs triage | Request to prevent setting build-base on stable bases for platforms charms, including documentation updates. Issue remains unlabelled and inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
20
Confidence:
85
Support Request:
0
|
close stale | Request to prevent setting build-base on stable bases. Unlabelled and author is a maintainer, but has seen no progress or maintainer engagement in over two years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #915 Enforce that the build and run base are the same* base | craft-application | open | Maintainer request to reject mismatched build-base/base pairs, with exceptions for bare, development, legacy overrides, and base snaps; still open. |