Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

action-setup V2 issue: ERR_PNPM_META_FETCH_FAIL #136

Closed
ImPrankster opened this issue Jul 4, 2024 · 5 comments
Closed

action-setup V2 issue: ERR_PNPM_META_FETCH_FAIL #136

ImPrankster opened this issue Jul 4, 2024 · 5 comments

Comments

@ImPrankster
Copy link

Recently when running pnpm/action-setup@v2 in GitHub CI I got this error:

GET https://registry.npmjs.org/pnpm: Value of "this" must be of type URLSearchParams

Using node-version 20
It happens during self-install, seems to be a connection problem
It started about one day ago

@alokVishu
Copy link

I have also faced the same issue.

image

@BenjaminNolan
Copy link

BenjaminNolan commented Jul 4, 2024

Can confirm this started some time between now and 17:00 UTC yesterday, when it was working fine. I suspect NPM have put out an update which broke it, perhaps relating to the deprecation warning for registry.npmjs.org:

» curl -I https://registry.npmjs.org     
HTTP/2 200 
date: Thu, 04 Jul 2024 06:13:03 GMT
content-type: application/json
cf-ray: 89dcf7980d501bc4-MAD
cf-cache-status: DYNAMIC
npm-notice: This endpoint is deprecated. Use https://replicate.npmjs.com instead.
server: cloudflare

Edit: I didn't realise we were using v2 rather than v4, which seems to work, so the fix genuinely is "upgrade to v4" :)

@alokVishu
Copy link

updated pnpm/action-setup@v2 => pnpm/action-setup@v4 fix the issue

@dvins
Copy link

dvins commented Jul 4, 2024

Duplicate of #135.

The proposed "fix" is a work around and method of going forward provided GitHub workflows can be readily updated and approved. But it does not resolve stuck / failing workflow runs, many of which cannot be triggered again without additional code updates via merge or rebase of each one to pull in the use of the updated workflow action version.

DaPigGuy added a commit to Paroxity/FrameHub that referenced this issue Jul 4, 2024
frostime added a commit to siyuan-note/plugin-sample-vite-svelte that referenced this issue Jul 4, 2024
charlypoly added a commit to inngest/website that referenced this issue Jul 5, 2024
charlypoly added a commit to inngest/website that referenced this issue Jul 5, 2024
@zkochan
Copy link
Member

zkochan commented Jul 5, 2024

@zkochan zkochan closed this as completed Jul 5, 2024
meeroslav added a commit to nrwl/nx that referenced this issue Jul 24, 2024
…26838)

I just created a new nx monorepo with pnpm and in the github.ci file it
uses pnpm/action-setup@v2.
I ran into the following issue
pnpm/action-setup#136 and updating to
pnpm/action-setup@v4 solved the issue for me

---------

Co-authored-by: Jan-Niklas Wortmann <[email protected]>
Co-authored-by: Miroslav Jonaš <[email protected]>
ndcunningham pushed a commit to nrwl/nx that referenced this issue Jul 24, 2024
…26838)

I just created a new nx monorepo with pnpm and in the github.ci file it
uses pnpm/action-setup@v2.
I ran into the following issue
pnpm/action-setup#136 and updating to
pnpm/action-setup@v4 solved the issue for me

---------

Co-authored-by: Jan-Niklas Wortmann <[email protected]>
Co-authored-by: Miroslav Jonaš <[email protected]>
FrozenPandaz pushed a commit to nrwl/nx that referenced this issue Jul 24, 2024
…26838)

I just created a new nx monorepo with pnpm and in the github.ci file it
uses pnpm/action-setup@v2.
I ran into the following issue
pnpm/action-setup#136 and updating to
pnpm/action-setup@v4 solved the issue for me

---------

Co-authored-by: Jan-Niklas Wortmann <[email protected]>
Co-authored-by: Miroslav Jonaš <[email protected]>
(cherry picked from commit 9faeddc)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants