🌿🌿🌿🌿 4.2.0 BUG LMAOOO
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 217
- Avg merge
- 8h 42m
- Merged PRs (30d)
- 1
Description
Run pnpm/action-setup@v4
with:
dest: ~/setup-pnpm
run_install: null
package_json_file: package.json
standalone: false
/usr/bin/docker exec d056a040b6117a306edcfd11be8cd02a4c01d56b778fe24d31e7333822dcc2dc sh -c "cat /etc/*release | grep ^ID"
Running self-installer...
ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)
This error happened while installing a direct dependency of /github/home/setup-pnpm
Your Node version is incompatible with "xxxxxxxxxxxxxxxxxxxx/pnpm/10.13.1".
Expected version: >=18.12
Got: v16.20.2
This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.
Error: Something went wrong, self-installer exits with code 1
Installation Completed!
after releasing 4.2.0 we get this, pinning back to 4.1.0 solves issue
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
Review the 4.2.0 release changes and the pnpm/action-setup@v4 invocation shown in the report. Reproduce the failure with Node v16.20.2 and compare it with v4.1.0. Done when the regression is resolved for the affected environment or the required Node version is made explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, nodejs, typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100