-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: promote snap to candidate on release #94
chore: promote snap to candidate on release #94
Conversation
Promote snap to latest/candidate channels upon every GitHub release.
bdab19f
to
e873286
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, thanks.
Seems to follow the same approach as https://github.com/canonical/pebble/pull/255/files, so it LGTM
As for the new secret, either @jnsgruk or @niemeyer need to add it.
Double-quotes are not okay in a Github workflow expressions. Change back to single-quotes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. @niemeyer will need to add the creds as I don't have access.
Okay, that's done. I'll merge this now. Thanks all! |
In canonical#94, the workflow for promoting snaps from latest/edge to latest/candidate upon GitHub release, was introduced. We didn't have riscv64 builds for the snap back then. We have it now. [1] This commit extends the promotion workflow for the riscv64 architecture. References: - [1] https://answers.launchpad.net/launchpad/+question/707699
In canonical#94, the workflow for promoting snaps from latest/edge to latest/candidate upon GitHub release was introduced. We didn't have riscv64 builds for the snap back then. We have it now. [1] This commit extends the promotion workflow for the riscv64 architecture. References: - [1] https://answers.launchpad.net/launchpad/+question/707699
Promote snap to
latest/candidate
channels upon every GitHub release.Successfully executing this workflow job would require adding a
SNAPCRAFT_STORE_CREDENTIALS
secret in this repo. Please let me or @cjdcordeiro know if you don't have access to it (it's inside the credentials for the bot account).Similar to canonical/pebble#255.
Demo run: https://github.com/rebornplusplus/chisel/actions/runs/5925313450
(not exactly the same behaviour as the demo promoted to
latest/beta
and ran the workflow job onpush
)