Skip to content

Remove restriction for promoting edge releases with --yes #5958

Closed

Description

@mr-cal

Check existing issues

  • I've verified that this request isn't described by any existing issues.

Request

For the snapcraft promote command, drop the restriction that doesn't allow using --yes for edge releases.

Since this could break existing workflows that depend on this safety net, this should be part of Snapcraft 9.

The problem it solves

Users are artificially restricted from automatically promoting edge releases at the command line:

> snapcraft promote <snap-name> --from-channel edge --to-channel beta --yes
Error: 'edge' is not a valid set value for --from-channel when using --yes.

This is an unhelpful error and has forced users to create workarounds.

Removing this restriction is preferable to adding more flags (e.g. --allow-dangerous-promotion), which adds more complexity and is redundant with --yes.

Fixes:

Activity

  1. added this to the 9.0 milestone on Jan 16, 2026
  2. syncronize-issues-to-jira commented on Jan 16, 2026

    @syncronize-issues-to-jira

    Thank you for reporting your feedback to us!

    The internal ticket has been created: https://warthogs.atlassian.net/browse/SNAPCRAFT-1270.

    This message was autogenerated

  3. mr-cal commented on Jun 15, 2026

    @mr-cal
    CollaboratorAuthor

    This has been fixed in Snapcraft 9.0.

    Anyone using workarounds in a Github workflow like this:

    env:
        SNAPCRAFT_HAS_TTY: "true"
    run: |
      yes | snapcraft promote <snap-name> --from-channel latest/edge --to-channel latest/beta

    can use the --yes flag instead:

    run: |
      snapcraft promote <snap-name> --from-channel latest/edge --to-channel latest/beta --yes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions