Packages pushed via snapcraft and published on the website ends up having no channel
Metadata
Current evaluation
The Store website was fixed and released to prevent revisions from being published without a channel; maintainers confirmed no Snapcraft change was needed.
Resolution: closed resolved
Reason: Caio Begotti closed the report after confirming on 2016-10-06 that the website fix had been released and prevented channel-less publication; no Snapcraft change was required.
Evaluated by: mr-cal-bot
No scores available.
Issue body
We can end up with published package assigned to no channel (without the user noticing). This state shouldn't be available to the user as I've seen some developers getting stuck and not understand what's happening.
Steps to reproduce:
- register a snap name (via snapcraft or the website)
- snapcraft push <your_snap>
- go to the website, to the snap revision and publish it
-> this snap is published without having any channel assigned.
It would be intersting to know how many snaps are in that state and maybe contact their developers? (I knew at least of one, who got it fixed).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | The Store website was fixed and released to prevent revisions from being published without a channel; maintainers confirmed no Snapcraft change was needed. | |
| stealth/space-bunny-alpha | — | closed resolved | The Store website was fixed to prevent revisions being published without a channel; maintainers confirmed the release and said no Snapcraft change was needed. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a recorded fix or linked PR after 16 days of inactivity; channelless website publication remained unresolved. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Snaps published via the website ending up with no channel assignment remain unfixed and unaddressed. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. Snaps published via the website after a snapcraft push could end up unassigned to any channel, causing developer confusion. No fix was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Snaps published via snapcraft or the website can end up with no assigned channel. The report was closed without resolution or fix, indicating it was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. Published snaps could incorrectly lack an assigned channel, causing developer confusion. No fix was implemented or discussion provided. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1621713 snapcraft release doesn't match the spec | snapcraft (launchpad) | closed | Snapcraft now correctly handles revision arguments and channel updates; the maintainer confirmed the outdated release behavior is resolved. |