docs: document automatic Node.js setup for self-hosted/GPU runners - #47234
Merged
Conversation
…ents Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add early Node.js runtime validation for self-hosted GPU workflow runners
docs: document automatic Node.js setup for self-hosted/GPU runners
Jul 22, 2026
pelikhan
approved these changes
Jul 22, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Documents automatic Node.js provisioning for non-standard runners.
Changes:
- Explains runner-specific Node.js behavior.
- Shows a
runtimes.node.versionoverride. - Notes automatic setup behavior.
Show a summary per file
| File | Description |
|---|---|
docs/src/content/docs/reference/self-hosted-runners.md |
Documents Node.js requirements and compiler setup behavior. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Medium
| ``` | ||
|
|
||
| > [!NOTE] | ||
| > The automatic Node.js setup is emitted only for non-standard runners. If your self-hosted runner already has Node.js installed and on `PATH`, the `actions/setup-node` step still runs but is a no-op when the requested version is already present. |
This was referenced Jul 22, 2026
Contributor
|
🎉 This pull request is included in a new release. Release: |
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
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.
Self-hosted and GPU runners frequently lack Node.js on
PATH, causing workflows to fail late withnode: command not found— wasting credits and producing cryptic errors.What's already in the codebase
The compiler already handles this automatically (added in the base branch):
isCustomImageRunner()detects non-standard runners (self-hosted, GPU labels, enterprise runners, array/objectruns-onforms)DetectRuntimeRequirements()injectsactions/setup-node(Node.js 24) early in the agent job for any non-standard runnerubuntu-latest,ubuntu-22.04, etc.) are allowlisted and unchangedThis PR
Adds a Node.js subsection to the Runner environment requirements section of
self-hosted-runners.md, documenting the automatic setup behavior:actions/setup-nodebefore any agent or framework scriptsruntimes:frontmatter: