From 3dcab7061f73a225c92e0ee54240f35c3c34fdf1 Mon Sep 17 00:00:00 2001 From: Dmitry Ratushnyy <132273757+dmitry-ratushnyy@users.noreply.github.com> Date: Fri, 27 Oct 2023 08:54:21 +0200 Subject: [PATCH] Update release workflow (#284) ## Issue 1. Currently the ci job for releasing charm named in a confusing manner 2. Publishing charm to 6/edge is failing with `latest/edge` charmcraft ## Solution 1. Rename ci workflow for releasing 2. Use `latest/stable` for release charm --------- Co-authored-by: Dmitry Ratushnyy --- .github/workflows/release.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml index 304e87f53..9e7b9790c 100644 --- a/.github/workflows/release.yaml +++ b/.github/workflows/release.yaml @@ -1,4 +1,4 @@ -name: Release to latest/edge +name: Release to 6/edge on: push: @@ -19,7 +19,7 @@ jobs: name: Build charm uses: canonical/data-platform-workflows/.github/workflows/build_charm_without_cache.yaml@v5 with: - charmcraft-snap-channel: "latest/edge" + charmcraft-snap-channel: "latest/stable" release: name: Release charm