feat(projects): validate component names do not begin with 'snap-'
Metadata
Current evaluation
Merged validation preventing component names from starting with 'snap-', reserved for snapd. Approved by two reviewers, passed CI, and resolves #4538. Unrelated CI failures were addressed in separate PRs.
Suggested action: —
No scores available.
Issue body
- [x] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `tox run -m lint`?
- [x] Have you successfully run `tox run -e test-py310`? (supported versions: `py39`, `py310`, `py311`, `py312`)
-----
Components beginning with `snap-` are reserved for future use by `snapd`.
Fixes #4538
(CRAFT-2419)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged validation preventing component names from starting with 'snap-', reserved for snapd. Approved by two reviewers, passed CI, and resolves #4538. Unrelated CI failures were addressed in separate PRs. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged. Implements validation to reject component names starting with 'snap-', reserving the prefix for snapd. Resolves #4538. Tests passed with full coverage; unrelated CI failures were addressed in separate PRs. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4538 Validate component names do not begin with `snap-` | snapcraft | closed | Fixed via PR #4566. Added validation to reject component names in snapcraft.yaml starting with snap-, as these are reserved for snapd. | |
| #4945 feat: allow numbers in component names | snapcraft | merged | Merged to allow digits in component names and unify validation with snap names. Fixes Launchpad bug #2069783. Approved by two reviewers, CI passed after fixing a doc reference, and depends on craft-parts PR #790. |