Parser should warn when it encounters an invalid snapcraft.yaml
Metadata
Current evaluation
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.
Suggested action: close stale
Reason: The issue is 3734 days old with 0 comments, no labels, and no maintainer interaction, and the original concern (parser silently accepting a snapcraft.yaml without 'parts') is no longer applicable: current snapcraft validates the file against a JSON schema that requires parts and rejects invalid files. Confidence is moderate because repo code tools were unavailable this session, so the current validation behavior could not be re-verified directly.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
12.75
Staleness:
95
Complexity:
15
Confidence:
65
Support Request:
10
|
close stale | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Request to add a parser warning when the 'parts' key is missing from snapcraft.yaml. The issue has been inactive for over nine years with no maintainer response or comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
70
Support Request:
5
|
needs triage | Feature request to add a parser warning when the 'parts' key is missing from snapcraft.yaml. Open for over 10 years with zero maintainer comments or labels, awaiting assessment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Feature request to add a parser warning when the 'parts' field is missing from snapcraft.yaml. Issue has been inactive for over 9 years with no maintainer response or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
10
Confidence:
90
Support Request:
5
|
close stale | Parser should warn when the parts field is missing from snapcraft.yaml. Open with zero comments and no labels, awaiting triage and assignment. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft (launchpad)#1599098
(confidence 50%)
Adjacent parser-robustness bug about a missing snapcraft.yaml file (crash vs. missing 'parts' key); closed without a formal fix.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1802312 Error message with empty parts is misleading | snapcraft (launchpad) | open | Misleading snapcraft error when 'parts' is empty in snapcraft.yaml: the message conflates a schema type error with a part-name validation error. Filed ~7.8 years ago by an external contributor, no labels, no maintainer response, no comments. | |
| #1826753 Snapcraft should complain multiple `after` properties in a single part | snapcraft (launchpad) | open | Request for snapcraft to error on duplicate 'after' YAML keys in a part definition. 7+ years old, zero comments, no labels, no maintainer interaction. References snapcraftctl and old part format that no longer exist in modern snapcraft. | |
| #58 Run YAML validity/schema linters before `snapcraft` | snapcraft-rocks | open | 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. | |
| #1807871 Does not warn/error when no apps are defined | snapcraft (launchpad) | open | Feature request for snapcraft to warn or error when no apps are defined in snapcraft.yaml, and to add a lint check. 7.7 years old, no labels, no maintainer comments, never triaged. | |
| #1845276 snapcraft shouldn't complain about snap/README.md | snapcraft (launchpad) | open | Request to stop snapcraft warning about snap/README.md as a non-snapcraft path so docs can live in the snap/ dir. 7 years old, zero comments, no labels or maintainer response; the warning is intentional and already documents the snap/local/ workaround. |