Validate component names do not begin with `snap-`
Metadata
Current evaluation
Fixed via PR #4566. Added validation to reject component names in snapcraft.yaml starting with snap-, as these are reserved for snapd.
Suggested action: —
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 |
|---|---|---|---|---|
| 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. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed via PR #4566. Added validation to reject component names starting with snap- in snapcraft.yaml, as these identifiers are reserved by snapd. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4566 feat(projects): validate component names do not begin with 'snap-' | snapcraft | merged | 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. |