Validate component names do not begin with `snap-`
Metadata
Current evaluation
Merged PR #4566 added validation rejecting snapcraft.yaml component names beginning with the snapd-reserved prefix "snap-".
Resolution: closed resolved
Reason: PR #4566 was merged and implemented the requested validation. Maintainer mr-cal confirmed in the closing comment that #4538 was fixed via #4566.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
Component names in a `snapcraft.yaml` cannot begin with `snap-`.
### Why it needs to get done
These names are reserved for `snapd`.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #4566 added validation rejecting snapcraft.yaml component names beginning with the snapd-reserved prefix "snap-". | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #4566, which validates that snapcraft.yaml component names do not begin with the snapd-reserved prefix "snap-". | |
| stealth/space-bunny-alpha | — | closed resolved | Component names starting with "snap-" are now rejected as reserved for snapd. Fixed by merged PR canonical/snapcraft#4566. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed via PR #4566. Added validation to reject component names in snapcraft.yaml starting with snap-, as these are reserved for snapd. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved via PR #4566. Validation was added to reject component names starting with snap- in snapcraft.yaml, as these identifiers are reserved for snapd. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed via #4566. Added validation to reject component names in snapcraft.yaml that begin with snap-, as these identifiers are reserved for snapd. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Validation implemented to reject component names starting with snap- in snapcraft.yaml, as these are reserved by snapd. Fixed via pull request #4566. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/snapcraft#4566
(confidence 100%)
Merged PR implementing validation for the reserved snap- prefix.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4566 feat(projects): validate component names do not begin with 'snap-' | snapcraft | merged | Merged PR #4566 to reject component names beginning with the snapd-reserved "snap-" prefix, fixing #4538; #4567 and #4568 addressed unrelated CI failures. | |
| #2069783 cannot create components with digits in the name | snapcraft (launchpad) | closed | Bug confirmed: component names rejected digits, though snapd allows them. Fixed by PR canonical/snapcraft#4945 (commit 8ab7fd0c8) sharing one validator for snap and component names, after upstream craft-parts#790 (b2128938). | |
| #4464 Parse and validate component keywords in `snapcraft.yaml` | snapcraft | closed | Component parsing, validation, and get_component_names() landed in 070c7e995 and shipped with core22 component support through merged PR #4654 (76e909dea). |