From b17e5499ebbe9765c52d7b1152f24eaf5098f2d3 Mon Sep 17 00:00:00 2001 From: ospab Date: Wed, 8 Jul 2026 18:18:11 +0300 Subject: [PATCH] ci: fix run-name to say "channel" instead of a bare branch name MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit run-name showed "release version nightly" / "release version pre-release" for every branch-push run — read exactly like the release TAG was bare "nightly"/"pre-release" (the bug fixed earlier), when the actual GH Release tag has been correctly versioned (e.g. "0.4.3-nightly") all along via resolve-channel. run-name can't reference job outputs (it's evaluated before any job runs), so it can't show the real computed tag directly — spell out "channel" instead so the label can't be mistaken for the release tag again. --- .github/workflows/release.yml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index a68f97d..0ea4312 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -1,6 +1,14 @@ name: CI/CD -run-name: "CI/CD: release version ${{ github.ref_name }}" + +# `run-name` is evaluated at workflow-start, BEFORE any job runs — it cannot +# see resolve-channel's computed tag_name (e.g. "0.4.3-nightly"), only the +# `github.*` context. The old "release version ${{ github.ref_name }}" showed +# the bare branch name ("nightly"/"pre-release") for every run, which reads +# exactly like a literal release tag and caused real confusion — the actual +# release tag has been correct (versioned) all along; only this label lied +# about it. Spell out "channel" so nobody mistakes one for the other again. +run-name: ${{ startsWith(github.ref, 'refs/tags/') && format('Release build: {0}', github.ref_name) || format('Release build: {0} channel', github.ref_name) }} on: push: