You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
failed when promote snap using option: --yes #4312
Thanks for the report. Is the error confusing? what we are essentially saying is that you shouldn't be auto promoting from edge as it is a moving target
@sergiusens Yeah a bit confusing to me, so this is a normal behavior by design? I want to automatically promote through cron tasks. Is there any way to do this currently?
Not currently, but we can consider adding a flag like --enable-dangerous-promotion. Since edge is a moving target, there is no set that can be created from edge in a reliable way. We could also consider creating sets with version and/or build ids (launchpad and our action-build add these)
Activity
boukendesho commentedon Aug 10, 2023
snapcraft promote SNAP_NAME --from-channel edge --to-channel candidate --yes
drop the 'latest/' track name also got same error
sergiusens commentedon Aug 10, 2023
Thanks for the report. Is the error confusing? what we are essentially saying is that you shouldn't be auto promoting from edge as it is a moving target
boukendesho commentedon Aug 10, 2023
@sergiusens Yeah a bit confusing to me, so this is a normal behavior by design? I want to automatically promote through cron tasks. Is there any way to do this currently?
sergiusens commentedon Aug 11, 2023
Not currently, but we can consider adding a flag like
--enable-dangerous-promotion. Since edge is a moving target, there is no set that can be created fromedgein a reliable way. We could also consider creating sets with version and/or build ids (launchpad and our action-build add these)boukendesho commentedon Aug 11, 2023
@sergiusens ok, thx
krille-chan commentedon Sep 18, 2023
This got closed, does it mean that
--enable-dangerous-promotionis now implemented?mr-cal commentedon Jun 15, 2026
This has been fixed in Snapcraft 9.0.
Anyone using workarounds in a Github workflow like this:
can use the
--yesflag instead: