fix(prerelease-setup): remove ${{ }} expression from github-token input description#154
Open
sowmyav27 wants to merge 2 commits into
Open
fix(prerelease-setup): remove ${{ }} expression from github-token input description#154sowmyav27 wants to merge 2 commits into
sowmyav27 wants to merge 2 commits into
Conversation
…ut description
The github-token input description embedded the literal ${{ github.token }}
as example prose. GitHub evaluates every ${{ }} expression in an action
manifest, including input descriptions, and the 'github' context is not
available there, so the manifest failed template validation:
Unrecognized named-value: 'github' ... github.token
Both prerelease consumer jobs (vCluster, AI Cloud) use this action as their
first step, so they died at 'Set up job' before any step ran. Reword the
example to plain text so it is not parsed as an expression.
cbron
approved these changes
Jun 12, 2026
make check-docs regenerates action READMEs from action.yml via auto-doc. The previous commit changed the github-token input description but did not regenerate the README, so check-docs reported drift.
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
2 participants
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.
What
Reword the
github-tokeninput description inprerelease-setup/action.ymlso it no longer contains a literal${{ github.token }}expression.Why
GitHub evaluates every
${{ }}expression in an action manifest, includinginputs.*.description. Thegithubcontext is not available in that position, so the manifest fails template validation at load time:Both pre-release consumer jobs in loft-enterprise (
vCluster,AI Cloud) use this action as their first step, so they die at Set up job in ~4s before anything runs. This fires on every published vCluster Pro tag (e.g. the v0.35.0-rc.6 dispatch: loft-enterprise run 27443560408).The
${{ github.token }}was only meant as example prose for the caller; the real consumption (${{ inputs.github-token }}in the steps) is unaffected.Change
Documentation-only string; no behavior change.
After merge — required
The consumer pins
@prerelease-setup/v1, which currently points at the broken commit. Theprerelease-setup/v1tag must be force-moved to the fix commit (per docs/release process:git tag -f prerelease-setup/v1 && git push origin prerelease-setup/v1 --force), otherwise the workflow keeps loading the broken pinned version.