Can snapcraft commands default to base in snapcraft.yaml from build subdirectories?
Metadata
Current evaluation
Snapcraft does not discover a parent snapcraft.yaml from build subdirectories, so commands such as plugins use the latest base; the request remains open and untriaged.
Suggested action: needs triage
Reason: The report clearly describes the working-directory-dependent behavior and desired parent-project discovery. The current get_snap_project implementation only checks known project-file paths within the supplied directory, not parents; however, the report has no labels, maintainer response, exact output, or rules for nested projects and traversal boundaries.
Evaluated by: mr-cal-bot
Impact:
33
Quick Win:
10
Complexity:
46
Confidence:
84
Actionability:
55
Issue body
I can see that if I'm running commands like "snapcraft plugins", if I happen to be at the top of a snap build directory, then the command will use the base specified in the snapcraft.yaml file.
However, if I'm in some (non-snap/) subdirectory of that build directory, then the command reverts to simply using the latest supported base. Would it be difficult to extend snapcraft's behaviour to act more like Git, in that no matter where you are in a build directory, the base from the snapcraft.yaml file associated with that build directory will be used? That would be more consistent behaviour.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
33
Quick Win:
10
Complexity:
46
Confidence:
84
Actionability:
55
|
needs triage | Snapcraft does not discover a parent snapcraft.yaml from build subdirectories, so commands such as plugins use the latest base; the request remains open and untriaged. | |
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
14
Complexity:
45
Confidence:
82
Actionability:
72
|
needs triage | Untriaged feature request to make commands such as snapcraft plugins discover a parent snapcraft.yaml and honor its base when run from nested build subdirectories; no maintainer feedback. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
30
Quick Win:
21
Staleness:
95
Complexity:
30
Confidence:
60
Support Request:
20
|
needs triage | Feature request to make snapcraft commands use base from snapcraft.yaml when run from subdirectories of the build directory. Untriaged, 4 years old, zero maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Request to make snapcraft commands automatically detect and use the base from snapcraft.yaml when run from subdirectories, instead of defaulting to the latest supported base. Unanswered and inactive for over four years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Request to make snapcraft commands automatically detect and use the base from snapcraft.yaml when run from subdirectories. Currently inactive for ~4 years with no maintainer response or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Request to make snapcraft commands inherit the base from snapcraft.yaml when executed from subdirectories. Currently untriaged, zero comments, and inactive for nearly 4 years. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.