# actions/setup-node "Could not resolve dist for node-version-file"

> Fix actions/setup-node failing to resolve a Node version from node-version-file due to a missing or malformed file.

Source: https://latchkey.dev/learn/github-actions/actions-setup-node-could-not-resolve-dist-node-version-file  
Updated: 2026-06-26

setup-node reads the version from the path in node-version-file. A missing file, a path-not-checked-out, or a malformed value leaves no resolvable version.

## Diagnose it: was the cache hit, and was it the right one?

Cache bugs split into three shapes and they need different fixes: the cache never saved, it saved but the key never matches on restore, or it restored a stale entry through a `restore-keys` prefix and is now poisoning the build. The step output tells you which one you have.

```.github/workflows/ci.yml
- uses: actions/cache@v4
  id: cache
  with:
    path: ~/.npm
    key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
    restore-keys: |
      ${{ runner.os }}-npm-

- name: What happened
  run: |
    echo "exact hit: ${{ steps.cache.outputs.cache-hit }}"
    echo "key used:  ${{ steps.cache.outputs.cache-matched-key }}"
```

> `cache-hit` is only `true` on an exact key match. A `restore-keys` prefix match reports `cache-hit: false` while still restoring files, which is exactly how a stale cache gets mistaken for no cache at all.

## Cache limits that produce confusing failures

- Repository cache is capped at 10 GB. Past that, GitHub evicts least-recently-used entries, so a large cache can silently stop persisting.
- Caches are scoped by branch. A cache written on a feature branch is not visible to another feature branch, only to its base and its own descendants.
- An entry not read for 7 days is evicted, so a rarely-run workflow effectively never has a warm cache.
- Restoring a cache built for a different tool version is worse than a cold start, because you get a corrupted tree instead of a clean install. Always include the tool version in the key.

## FAQ

### What causes actions/setup-node "Could not resolve dist for node-version-file"?

There are 2 common causes: file missing or not checked out and malformed version value. The repo was not checked out, or the path does not point at the version file.

### How do I fix actions/setup-node "Could not resolve dist for node-version-file"?

Checkout first and point at a valid file. Run actions/checkout before setup-node.

### What does actions/setup-node "Could not resolve dist for node-version-file" actually mean?

The setup-node step fails with "Could not resolve a version" or cannot find node-version-file.

### How do I stop actions/setup-node "Could not resolve dist for node-version-file" happening again?

Always checkout before any setup-* that reads a repo file. The prevention section lists 2 changes that keep it from recurring.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt