cicd
runtime_version
ai_generated
true
Error: Version 19.x not found. Available versions: 18.x, 20.x, 22.x
ID: cicd/gha-node-version-mismatch
93%Fix Rate
92%Confidence
50Evidence
2023-01-01First Seen
Version Compatibility
| Version | Status | Introduced | Deprecated | Notes |
|---|---|---|---|---|
| any | active | — | — | — |
Root Cause
The actions/setup-node step cannot find the requested Node.js version. Occurs when specifying EOL versions, odd-numbered versions, or versions not yet available on the runner.
genericWorkarounds
-
95% success Use an LTS version specifier or .nvmrc file with setup-node
Set 'node-version: 20' or 'node-version: lts/*' in actions/setup-node, or create a .nvmrc file and use 'node-version-file: .nvmrc'
-
92% success Check available versions and use a supported major version
Use only even-numbered LTS versions (18, 20, 22). Check https://github.com/actions/node-versions/releases for available versions on GitHub runners
Dead Ends
Common approaches that don't work:
-
Pin to a very specific patch version like 18.17.1 without checking availability
55% fail
Specific patch versions may not be available on GitHub-hosted runners; the version manifest is updated independently
-
Manually install Node.js from source in a run step
75% fail
Compiling from source is extremely slow, fragile in CI, and conflicts with the runner's pre-installed tools
Error Chain
Leads to:
Preceded by:
Frequently confused with: