Summary
pnpm/setup@v2 (pinned 84cb39b, tag v2.0.2) resolved a devEngines.packageManager range of >=11 to pnpm 11.22.0, downloaded it via get-pnpm, but the extracted binary reported version 11.21.0 when run with --version — failing the action's post-download sanity check.
Where it happened
Failed run: https://github.com/hyunbinseo/neis-school-info/actions/runs/31900129059
Failed step: pnpm/setup@84cb39b217b10273981911c288cd62326dc7c6d2 (v2.0.2)
package.json
"devEngines": {
"packageManager": { "name": "pnpm", "version": ">=11", "onFail": "download" }
}
Log
Installing pnpm...
Downloading pnpm 11.22.0 from the npm registry
==> Downloading pnpm 11.22.0
Error: The installed pnpm reports version 11.21.0, expected 11.22.0
Timing
pnpm@11.22.0 published to npm at 2026-08-15T17:15:57.450Z.
- This run's
pnpm/setup step started at 2026-08-15T18:04:51Z, ~49 minutes later.
Hypothesis
The download passed get-pnpm's signature/checksum verification, so this isn't corruption — likely a propagation race between the registry packument and the served binary shortly after release.
Suggestion
Retry with backoff when the post-download version check fails for a range/dist-tag spec (not an exact pin), since that mismatch is more likely transient than real corruption.
Summary
pnpm/setup@v2(pinned84cb39b, tag v2.0.2) resolved adevEngines.packageManagerrange of>=11to pnpm11.22.0, downloaded it viaget-pnpm, but the extracted binary reported version11.21.0when run with--version— failing the action's post-download sanity check.Where it happened
Failed run: https://github.com/hyunbinseo/neis-school-info/actions/runs/31900129059
Failed step:
pnpm/setup@84cb39b217b10273981911c288cd62326dc7c6d2(v2.0.2)package.json
Log
Timing
pnpm@11.22.0published to npm at2026-08-15T17:15:57.450Z.pnpm/setupstep started at2026-08-15T18:04:51Z, ~49 minutes later.Hypothesis
The download passed
get-pnpm's signature/checksum verification, so this isn't corruption — likely a propagation race between the registry packument and the served binary shortly after release.Suggestion
Retry with backoff when the post-download version check fails for a range/dist-tag spec (not an exact pin), since that mismatch is more likely transient than real corruption.