No error if `after` specifies part that doesn't exist
Metadata
Current evaluation
Closed without a fix or comments, indicating the bug was abandoned. Snapcraft continues to silently accept invalid after references to non-existent parts.
Suggested action: —
No scores available.
Issue body
Snapcraft is perfectly happy running with the following YAML snippet:
parts:
part1:
plugin: nil
after: [no-such-part]
part2:
plugin: nil
Note that `no-such-part` isn't defined. This should be an error. I suspect this is left over from the remote parts logic.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without a fix or comments, indicating the bug was abandoned. Snapcraft continues to silently accept invalid after references to non-existent parts. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. Closed without resolution due to prolonged inactivity. Validation for missing after dependencies was never implemented. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #539 Part dependency names not validated | craft-parts | closed | Closed without resolution. Missing validation for non-existent parts in the after keyword caused silent failures instead of errors. No fix or merge details provided. | |
| #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. | |
| #2386 project_loader: raise error if part in after is undefined | snapcraft | merged | Merged a fix that raises an error when an undefined part is referenced in the after keyword, resolving LP: #1799596. Previously, snapcraft silently ignored such references, complicating migration from remote parts. | |
| #2033882 snapcraft first run doesn't verify parts in parts after keyword on core22 | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft fails to validate non-existent parts in the after keyword on core22, a regression from core20, remains unaddressed. |