Wrong source-type in yaml is ignored
Metadata
Current evaluation
Closed without a documented fix or PR. Invalid source-type values in snapcraft.yaml remain silently ignored, suggesting the bug was abandoned or resolved upstream without tracking.
Suggested action: —
No scores available.
Issue body
When you are using an invalid source-type in snapcraft.yaml, it is ignored and no error is printed.
To reproduce, use a yaml with this in one part:
plugin: dump
source: .
source-type: nothing
It will successfully snap. I expect this to fail.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without a documented fix or PR. Invalid source-type values in snapcraft.yaml remain silently ignored, suggesting the bug was abandoned or resolved upstream without tracking. | |
| qwen/qwen3.6-35b-a3b | — | — | Invalid source-type values in snapcraft.yaml were silently ignored. The report was abandoned and closed without resolution, with no comments or pull requests. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The invalid source-type validation bug was abandoned due to inactivity, with no fix or discussion recorded. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as stale due to inactivity. The invalid source-type validation bug remains unfixed. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1276 sources: validate unknown source-type in yaml | snapcraft | closed | Closed without merging due to unresolved review comments and a failing CLA check caused by an email mismatch. The proposed validation for unknown source types in snapcraft.yaml was abandoned. | |
| #1741952 Unhandled source type provides traceback | snapcraft (launchpad) | closed | Closed. Missing source-type parameters triggered raw ValueErrors instead of SnapcraftErrors. No fix or PR was linked, indicating the report was likely abandoned or resolved in a later release without explicit tracking. | |
| #1807875 Wrong error when no source specified | snapcraft (launchpad) | closed | Closed without resolution. Reported a misleading error when the source field was omitted from snapcraft.yaml, which should explicitly require the source instead of failing on command execution. | |
| #1816397 Modifying snapcraft.yaml with parts using local sources get dirty | snapcraft (launchpad) | closed | Closed without resolution or comments. Appears abandoned, with no fix or workaround implemented. |