From 074b40e6ee5e29e6208f09a9cf33727ab7489529 Mon Sep 17 00:00:00 2001 From: Mario Limonciello Date: Sun, 19 Feb 2023 23:39:55 -0600 Subject: [PATCH] snap: restore automatic promotion, but to candidate channel Snap is switched to confined but we have to worry about timing our next release with the new snapd which can work with it. When we issue our next release we do want to get a binary saved at least, so let's promote to the 'candidate' channel come release time. This effectively reverts commit 57282a59033bd0e6cbb639a63a6a062e26dceabf. When the new snapd is out and we're happy enough with the results we can switch this back to automatic promotion to the stable channel again. --- .github/workflows/snap-candidate.yml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 .github/workflows/snap-candidate.yml diff --git a/.github/workflows/snap-candidate.yml b/.github/workflows/snap-candidate.yml new file mode 100644 index 000000000..2b576cb9d --- /dev/null +++ b/.github/workflows/snap-candidate.yml @@ -0,0 +1,14 @@ +name: Publish to snap candidate channel + +on: + release: + types: [published] + +jobs: + snap: + uses: ./.github/workflows/snap.yml + with: + deploy: true + channel: candidate + secrets: inherit +