ci(node): make the npm-publish tag optional, default to latest master

The workflow_dispatch `tag` input is now optional: blank builds the latest
master (checking out the dispatch ref and deriving the npm version from the
workspace Cargo.toml), or pass a tag to build that release instead. An explicit
`version` input still overrides either.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L7XwjsWSHWjrh39JxMLuB3

Author: claude

.github/workflows/npm-publish.yml

@@ -5,10 +5,12 @@
 # package plus per-platform `optionalDependencies` (fleischwolf-<triple>) via
 # napi-rs and publishes them all.
 #
-# Trigger: manual only (workflow_dispatch). Pick the release tag to build — the
-# workflow checks out that tag and publishes the npm version derived from it, so
-# npm releases stay decoupled from the crates.io release on every master push.
-# Run it from the Actions tab (or `gh workflow run npm-publish.yml -f tag=v0.7.0`).
+# Trigger: manual only (workflow_dispatch). By default it builds the latest
+# master (the version in the workspace Cargo.toml); optionally pass a release
+# tag to build that instead. Either way the workflow checks out the chosen ref
+# and publishes, so npm releases stay decoupled from the crates.io release on
+# every master push. Run it from the Actions tab (or
+# `gh workflow run npm-publish.yml`, optionally `-f tag=v0.7.0`).
 #
 # Requires one repository secret: NPM_TOKEN — an npm automation token with
 # publish rights to `fleischwolf` and the `fleischwolf-*` platform packages.
@@ -19,15 +21,16 @@ on:
   workflow_dispatch:
     inputs:
       tag:
-        description: "Release tag to build and publish (e.g. v0.7.0)."
-        required: true
+        description: "Release tag to build (e.g. v0.7.0). Blank = latest master."
+        required: false
+        default: ""
       version:
-        description: "Override the npm version (e.g. 0.7.0). Blank = derive from the tag."
+        description: "Override the npm version (e.g. 0.7.0). Blank = tag, or workspace version on master."
         required: false
         default: ""
 
 concurrency:
-  group: npm-publish-${{ inputs.tag }}
+  group: npm-publish-${{ inputs.tag || github.ref }}
   cancel-in-progress: false
 
 defaults:
@@ -57,7 +60,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
         with:
-          ref: ${{ inputs.tag }}
+          ref: ${{ inputs.tag || github.ref }}
 
       - uses: dtolnay/rust-toolchain@stable
         with:
@@ -113,7 +116,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
         with:
-          ref: ${{ inputs.tag }}
+          ref: ${{ inputs.tag || github.ref }}
 
       - uses: actions/setup-node@v4
         with:
@@ -137,14 +140,21 @@ jobs:
           name: js-binding
           path: crates/fleischwolf-node
 
-      # Version = the explicit override, else the selected tag with its leading `v`.
+      # Version = the explicit override, else the selected tag (sans leading `v`),
+      # else the workspace version from the root Cargo.toml (latest-master run).
       - name: Resolve version
         id: ver
         run: |
           v="${{ inputs.version }}"
-          if [ -z "$v" ]; then v="${{ inputs.tag }}"; v="${v#v}"; fi
+          if [ -z "$v" ]; then
+            if [ -n "${{ inputs.tag }}" ]; then
+              v="${{ inputs.tag }}"; v="${v#v}"
+            else
+              v="$(grep -m1 '^version = ' ../../Cargo.toml | sed -E 's/.*"([^"]+)".*/\1/')"
+            fi
+          fi
           echo "version=$v" >> "$GITHUB_OUTPUT"
-          echo "Publishing fleischwolf@$v from tag ${{ inputs.tag }}"
+          echo "Publishing fleischwolf@$v (ref: ${{ inputs.tag || github.ref }})"
 
       # Skip cleanly if this version is already on npm (idempotent re-runs).
       - name: Check if already published

crates/fleischwolf-node/README.md

@@ -23,8 +23,9 @@ Prebuilt platforms: Linux x64 / arm64 (glibc), macOS x64 / arm64, Windows x64.
 The right binary is pulled in automatically as a platform-specific
 `optionalDependency` (`fleischwolf-<triple>`). Releases are published to npm by
 manually running the `npm publish` workflow
-(`.github/workflows/npm-publish.yml`) for a chosen release tag — decoupled from
-the crates.io release.
+(`.github/workflows/npm-publish.yml`) — by default it builds the latest master
+(the workspace version); optionally pass a release tag to build that instead.
+Decoupled from the crates.io release.
 
 ## Build from source