← Back to issue list

Not possible to close a channel for only a specific architecture

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1752459
Type
issue
State
open
Author
~popey
Labels
—
Created
Updated
Closed
—

Current evaluation

Acknowledged gap: `snapcraft close` (snapcraft/commands/manage.py) accepts only name+channel and posts {"channels":[channel]} to /dev/api/snaps/<id>/close, closing all arches; no arch-scoped close exists and store API lacks it. Workaround: close then reopen other arches.

Suggested action: keep open

Reason: Maintainers confirmed the gap: kyrofa wrote "Looking at the store API docs, this doesn't look possible today" and sergiusens replied "We will need to write a user story for this... more of an 'unrelease' scenario", yet no implementation exists in current code (StoreCloseCommand still only takes name/channel and StoreClientCLI.close calls release() with revision=None, i.e. every arch). The reported behaviour is working as designed by the store, but it is a valid, acknowledged unrelease capability gap, not a bug to close; a partial workaround was documented in 2020 (close everything, then reopen only the arches to keep), which caps impact below major. Age alone is not a closure reason.

Evaluated by: mr-cal-bot

Impact: 45 Quick Win: 8 Complexity: 65 Confidence: 78 Actionability: 50

Issue body

Build a snap and accidentally release it to the stable channel on an architecture other than the one your primary workstation runs. (e.g. workstation is amd64, you published arm64). There seems to be no straightforward way to close a channel. "snapcraft close snapname" works fine for your workstation arch, but no good for closing the accidental release to stable on arm64. How is a developer supposed to undo these kinds of mistakes?

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 45
Quick Win: 8
Complexity: 65
Confidence: 78
Actionability: 50
keep open Acknowledged gap: `snapcraft close` (snapcraft/commands/manage.py) accepts only name+channel and posts {"channels":[channel]} to /dev/api/snaps/<id>/close, closing all arches; no arch-scoped close exists and store API lacks it. Workaround: close then reopen other arches.
stealth/space-bunny-alpha
Impact: 38
Quick Win: 8
Complexity: 55
Confidence: 78
Actionability: 48
keep open Feature request: `snapcraft close` closes a channel for all architectures, with no way to close only one arch's release. Acknowledge as an 'unrelease' gap; store API reportedly lacks support; 2020 comment notes a close-then-reopen workaround.
qwen/qwen3.6-35b-a3b
Impact: 40
Quick Win: 12
Complexity: 50
Confidence: 70
Actionability: 60
keep open Feature request to close a channel for a specific architecture. User reports snapcraft close only works for workstation arch. Open 8.5 years with no maintainer response.
qwen/qwen3.8-27b
Impact: 30
Quick Win: 18
Staleness: 90
Complexity: 40
Confidence: 65
Support Request: 15
needs triage Request to close a snap channel for a specific architecture only (e.g. undo accidental stable release on arm64). Open ~8.5 years, zero comments, no labels, no maintainer engagement. Related Launchpad bug #1732501 still open.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 15
Confidence: 85
Support Request: 10
close stale Reports missing CLI functionality to close a specific architecture channel in snapcraft. Unaddressed for over 8 years with no comments or maintainer interaction.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 30
Confidence: 85
Support Request: 75
close stale Reports inability to close a snap channel for a specific architecture using snapcraft, asking how to revert an accidental release. The issue has no comments, labels, or maintainer interaction for over 8 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 30
Confidence: 60
Support Request: 40
close stale Reporter cannot close a snap channel for a specific architecture using snapcraft CLI. Issue is over 8 years old with no maintainer response or labels.

Update history

Date Change
created

Related work

  • Duplicate Of: snapcraft (launchpad)#1732501 (confidence 92%)

    Near-identical open bug ('it's not possible to close a channel for only one architecture', filed ~3 months earlier) describing the same missing arch-scoped close; the two should be merged.

Related issues

Issue Project State Summary Similarity
#1732501 it's not possible to close a channel for only one architecture snapcraft (launchpad) open Architecture-specific channel closing remains unimplemented and open: snapcraft close still targets all architectures, while the Store API has no scoped close operation.
88%
#6520 feat(store): close a channel for specific architectures snapcraft open Adds --arch flag to snapcraft close to close channels per-architecture. New feature, 5 days old, no review yet, CI mostly passing with one failing security scan.
72%