From 244d3ad374d58e52df31df8a8cc98f2446d201ae Mon Sep 17 00:00:00 2001 From: ospab Date: Thu, 9 Jul 2026 01:24:43 +0300 Subject: [PATCH] ci: update GHA run-name format for releases --- .github/workflows/release.yml | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index a0e8b52..30c03c3 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -1,6 +1,19 @@ 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. +# NOTE: this value MUST be quoted. The GHA string literal below contains +# "Release build: {0}" — an unquoted YAML plain scalar treats ": " (colon +# then space) as starting a nested mapping, which is exactly what broke every +# single push since this line was introduced: GitHub rejected the whole +# workflow file at parse time (before any job runs), silently burning an +# Actions-minutes-billed run per push for nothing. +run-name: "${{ startsWith(github.ref, 'refs/tags/') && (contains(github.ref_name, 'beta') && format('CI/CD: beta version {0}', github.ref_name) || contains(github.ref_name, 'nightly') && format('CI/CD: nightly version {0}', github.ref_name) || format('CI/CD: release version {0}', github.ref_name)) || format('CI/CD: {0} channel build', github.ref_name) }}" on: push: