Unable to release classic snap to beta channel
Metadata
Current evaluation
Users are blocked when snapcraft release returns only “Package is not ready to be published”; maintainers traced this to the store’s InconsistentStateError, with no actionable reason or resolution yet.
Suggested action: keep open
Reason: The report is valid and has maintainer acknowledgement: @sergiusens said the message comes directly from the store, and @roadmr identified it as an InconsistentStateError and asked whether its payload contains enough state to explain the failure. No resolving commit or PR is evidenced, and the current repository delegates store operations to craft-store, so the issue remains open for upstream error-detail investigation.
Evaluated by: mr-cal-bot
Impact:
42
Quick Win:
12
Complexity:
58
Confidence:
80
Actionability:
68
Issue body
Snap release is unhelpful:
$ snapcraft release wal-e 1 beta
Package is not ready to be published.
The bug is that 'snapcraft release' is not telling me *why* the package is not ready to be published. I am left blocked, with no hint on how to proceed.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
12
Complexity:
58
Confidence:
80
Actionability:
68
|
keep open | Users are blocked when snapcraft release returns only “Package is not ready to be published”; maintainers traced this to the store’s InconsistentStateError, with no actionable reason or resolution yet. | |
| stealth/space-bunny-alpha |
Impact:
48
Quick Win:
15
Complexity:
55
Confidence:
84
Actionability:
68
|
keep open | Open report: snapcraft release returns a generic 'not ready to be published' error instead of explaining blockers such as manual review; maintainers traced it to the Store's InconsistentStateError. | |
| stealth/space-bunny-alpha |
Impact:
44
Quick Win:
11
Complexity:
61
Confidence:
86
Actionability:
66
|
keep open | Classic snap releases can fail with an opaque Store message that does not explain why a revision cannot be released; the underlying Store error payload remains unresolved. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
13
Complexity:
30
Confidence:
60
Actionability:
60
|
needs triage | snapcraft release command shows unhelpful error 'Package is not ready to be published' without explaining why. Issue is 9+ years old, unlabelled, with no maintainer response or comments. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
21
Staleness:
95
Complexity:
40
Confidence:
55
Support Request:
15
|
close stale | snapcraft release prints only 'Package is not ready to be published' with no reason, blocking the user from releasing a classic snap to beta. No labels, no comments, no maintainer response; inactive for ~6 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
25
Confidence:
90
Support Request:
10
|
close stale | Report that snapcraft release command fails with an unhelpful error message lacking details on why a package isn't ready for publishing. No maintainer response or activity in over 6 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
90
Support Request:
20
|
close stale | snapcraft release fails with an unhelpful error message when publishing a classic snap, providing no details on why the package isn't ready. Issue is over 9 years old with no maintainer response or comments. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Reports unclear error message when releasing a classic snap to beta. No maintainer response, no labels, inactive for years. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.