fix(ci): source release tag from github.ref_name on all self-hosted runners - #221
Merged
Conversation
added 2 commits
June 24, 2026 18:50
The Windows release job failed at 'write version files' with 'GITHUB_REF_NAME is not set' on the org-level self-hosted win runner, while the Linux runner saw the variable fine. $env:GITHUB_REF_NAME is only injected by Actions runner >= 2.290, so an older self-hosted runner leaves it empty. Source the tag from the github.ref_name context (evaluated by Actions before the step runs) via a job-level REF_NAME env var instead, so the build no longer depends on the runner version. Replaces all three $env:GITHUB_REF_NAME usages (version step + both build steps).
The Linux release job failed at 'write version files' with the same empty-GITHUB_REF_NAME cause as Windows: the wsl2 self-hosted runner is also older than 2.290. macOS uses the same pattern and the same class of runner, so fix all three release workflows consistently to read github.ref_name from context via a REF_NAME env var.
thcp
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Every release job for
v0.7.0-alpha.17failed (or would fail) atwrite version files:Both the
winandwsl2self-hosted runners leave$GITHUB_REF_NAMEempty.Cause
GITHUB_REF_NAMEis injected by the runner, and only exists on Actions runner >= 2.290. Your self-hosted runners — recently re-registered at org level — are older, so the variable is empty. The previous runners that built alpha.16 had it.Fix
Read the tag from the
${{ github.ref_name }}context (evaluated by Actions before the step runs), via aREF_NAMEenv var, instead of the runner-injected$GITHUB_REF_NAME. Independent of runner version.Applied to all three release workflows for consistency, since all three run on the same class of self-hosted runner:
REF_NAME; version step + both build steps.Notes
release: published(or cutting alpha.18) after merge is needed to rebuild assets with the fixed workflows.🤖 Generated with Claude Code