core26: YAML error messages refer to core24
Metadata
Current evaluation
Fixed in #6447 so error messages for unsupported keys correctly reference the actual base (e.g., 'core26') instead of hardcoding 'core24'.
Resolution: closed resolved
Reason: Resolved by PR #6447, which updates validation logic to dynamically use the project's actual base in error messages instead of hardcoding 'core24'.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Check existing issues
- [x] I've verified that this bug isn't described by any existing issues.
### Bug description
When trying to use some features that were removed in core24, such as the `architectures` key, some Snapcraft error messages say `not supported for base 'core24'` even when base core26 is in use.
### Steps to reproduce
Run `snapcraft pack` on below YAML file.
### Environment
Snapcraft latest/edge on Ubuntu 26.04
### snapcraft.yaml
```yaml
name: core26-reproducer
base: core26
grade: devel
confinement: strict
architectures:
- build-on: amd64
build-for: amd64
```
### Log output
```shell
Bad snapcraft.yaml content:
- 'architectures' key is not supported for base 'core24'. Use 'platforms' key instead. (in field 'has-base.core26.architectures', input: [{'build-on': 'amd64', 'build-for': 'amd64'}])
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | closed resolved | Fixed in #6447 so error messages for unsupported keys correctly reference the actual base (e.g., 'core26') instead of hardcoding 'core24'. | |
| stealth/space-bunny-alpha |
Impact:
28
Quick Win:
15
Complexity:
35
Confidence:
88
Actionability:
82
|
keep open | core26/devel projects reusing core24's `architectures` rejection message get a hardcoded "not supported for base 'core24'" error. Hardcoded string still in models/project.py:2480; fix PR #6447 closed unmerged. | |
| stealth/space-bunny-alpha |
Impact:
27
Quick Win:
17
Complexity:
28
Confidence:
88
Actionability:
86
|
keep open | Error message when rejecting legacy 'architectures' key hardcodes 'core24' even for core26/devel/bare bases. Confirmed at snapcraft/models/project.py:2471; PR #6447 opened to name the actual base, not yet merged. | |
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
24
Complexity:
10
Confidence:
86
Actionability:
90
|
keep open | Snapcraft's core26 validation incorrectly names core24 when rejecting the legacy YAML `architectures` key. Triaged bug with a minimal reproducer; Jira ticket SNAPCRAFT-1370 was created. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
50
Quick Win:
40
Staleness:
45
Complexity:
20
Confidence:
85
Support Request:
0
|
keep open | Error message for unsupported 'architectures' key incorrectly says 'core24' when using base 'core26'. Triaged bug with clear reproduction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
10
Complexity:
15
Confidence:
90
Support Request:
5
|
keep open | Bug where Snapcraft error messages incorrectly reference base 'core24' when building with 'core26'. Triaged and awaiting fix. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
5
Complexity:
15
Confidence:
95
Support Request:
0
|
needs triage | Bug where Snapcraft error messages incorrectly reference base 'core24' when using 'core26'. Currently unlabelled and awaiting maintainer triage. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
0
Complexity:
20
Confidence:
90
Support Request:
0
|
needs triage | Bug report where Snapcraft error messages incorrectly reference core24 instead of core26 when using the core26 base. Unlabelled and awaiting maintainer triage. |
Update history
| Date | Change |
|---|---|
| closed | |
| updated | |
| updated |
Related work
-
Likely Fixed By:
snapcraft#6447
(confidence 100%)
PR #6447 explicitly addresses the hardcoded 'core24' error message issue.
Related issues
No related issues found above the similarity threshold.