Run YAML validity/schema linters before `snapcraft`
Metadata
Current evaluation
Feature request to run YAML validity/schema linters before snapcraft to catch typos like a missing base: key. Maintainer redirected it to snapcraft/craft-parts as not a bug in this repo; reporter asked for a move, but it has sat unlabelled and inactive for ~23 months.
Suggested action: close not a bug
Reason: Maintainer tigarmo explicitly triaged this and stated the missing-base handling and state-loading problems are 'a bug in Snapcraft, or craft-parts. I don't think it's a bug here,' so the request is misdirected to snapcraft-rocks. The reporter asked for it to be moved/reticketed but no action followed, and the issue has been unlabelled and inactive for ~23 months, so it should be closed here with a pointer to the correct repos rather than kept open.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
14.0
Staleness:
85
Complexity:
30
Confidence:
80
Support Request:
15
|
close not a bug | Feature request to run YAML validity/schema linters before snapcraft to catch typos like a missing base: key. Maintainer redirected it to snapcraft/craft-parts as not a bug in this repo; reporter asked for a move, but it has sat unlabelled and inactive for ~23 months. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | Feature request to add YAML linting before snapcraft execution. Maintainer redirected to Snapcraft/craft-parts over a year ago. No maintainer labels or follow-up. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
80
Support Request:
10
|
close not a bug | Suggests adding pre-snapcraft YAML validation to catch missing keys. Maintainer clarified validation belongs in Snapcraft itself and noted the issue is misplaced here, suggesting it be moved or reticketed. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
10
Confidence:
85
Support Request:
20
|
close stale | Suggests pre-running YAML linters before snapcraft to catch low-level errors like missing base keys. Maintainer notes this belongs in Snapcraft or craft-parts and recommends moving to those repos. Currently under discussion and awaiting triage. |
Update history
No update history recorded yet.
Related work
-
Caused By:
snapcraft-rocks#57
(confidence 85%)
The linter request originated from troubleshooting #57 (service exit code 70), which the reporter later attributed to an older snapcraft version producing state a newer version could not load.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1591207 Parser should warn when it encounters an invalid snapcraft.yaml | snapcraft (launchpad) | open | 2015-era feature request asking the snapcraft parser to warn when snapcraft.yaml is missing the 'parts' key. No labels, no comments, no activity for ~10 years. Modern snapcraft validates the file against a schema requiring parts, so the concern is outdated. |