action-setup@v6 does not take the requested pnpm version into account
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 217
- Avg merge
- 8h 42m
- Merged PRs (30d)
- 1
Description
It always installs pnpm v11
Repro: https://github.com/HRAshton/playground/actions/runs/24282365140/job/70906144585
Run pnpm/action-setup@v6
with:
version: 10
dest: ~/setup-pnpm
run_install: null
cache: false
cache_dependency_path: pnpm-lock.yaml
package_json_file: package.json
standalone: false
Running self-installer...
added 5 packages, and audited 6 packages in 3s
2 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
.../.bin/global/v11/8d4-19d7c7dadb0 | Progress: resolved 1, reused 0, downloaded 0, added 0
.../.bin/global/v11/8d4-19d7c7dadb0 | +2 +
.../.bin/global/v11/8d4-19d7c7dadb0 | Progress: resolved 2, reused 0, downloaded 2, added 2, done
Installation Completed!
--
Run pnpm --version
11.0.0-beta.4-1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the action-setup@v6 entry point and reproduce the linked GitHub Actions run, then compare the requested version, 10, with the installed version reported by pnpm --version. Trace how the action passes its version input to the installer. Done means requesting version 10 installs and reports pnpm 10 rather than v11.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100