From 01c96107447a11ebdf7f22c156e74682692faabe Mon Sep 17 00:00:00 2001
From: Simon KP <simon@keeperhub.com>
Date: Sat, 2 May 2026 18:15:26 +1000
Subject: [PATCH] ci(publish): strip literal expression syntax from workflow
 comment

The previous commit's explanatory comment included the literal text
'${{ }}' inside a shell # comment. GitHub Actions parses expression
syntax everywhere in the YAML before the run script reaches bash, so
the workflow file was rejected at parse time:

  Line 54, Col 14: An expression was expected

That dropped every push event on the workflow to 0-second failures.
Reword the comment to describe the same thing without the literal
expression markers.
---
 .github/workflows/publish.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
index 65a318d..c79e4cc 100644
--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@@ -57,8 +57,8 @@ jobs:
           # 76be751 to fire on wallet-v* tags but the strip below was
           # never updated, so v0.1.9 published cleanly while
           # wallet-v0.1.9 failed with a confusing tag-version mismatch.
-          # Env-only input ($REF_NAME from github.ref_name); no direct
-          # ${{ }} expansion in the script body.
+          # Env-only input -- REF_NAME is set in env: from github.ref_name;
+          # no direct expression-form expansion in the script body.
           TAG_VERSION="${REF_NAME##*-v}"
           TAG_VERSION="${TAG_VERSION#v}"
           PKG_VERSION="$(node -p "require('./package.json').version")"