Since about 6 hours ago I’ve started seeing the following error in my Github action netlify-cli deploy on my prod website: 05d4ff:9e2ffbde364a4ba294bc949da73e0dd4 deploy --dir=dist/site --functions=dist/functions --prod › ReferenceError: Response is not defined I can’t see any changes to my cod…

[image] mjgs: ReferenceError: Response is not defined I just discovered that I am able to deploy directly to Netlify using cli, but the error is blocking any deploys happening inside Github Actions, so all deploys across all my sites are currently blocked. Deploying directly bypassing Github…

22 hours since this started happening, and it’s still happening. Any ideas, hints, info on how I can troubleshoot to get it resolved? thks

I reset a fix branch to the main branch commit that was used to create the current live website. That’s a known good set of project files. …and the deploy error persists. Doesn’t that mean there must be something on the Netlify side that has changed, and that is blocking my deploys? Hello, is any…

I’ve run into the same issue. The github action is quietly failing with “ReferenceError: Response is not defined”. I didn’t even realize my last deploy of about 8 hours also failed.

Yeah thats exactly what happened to me. It fails silently which makes it even worse. I checked the netlify-cli action’s repo and they havent made any code changes in a very long time, which really points to something in the Netlify infra that is causing the error. Thanks for posting @srk i see you…

Thank you. I followed your input and used netlify cli for direct manual deploy. But that is definitely not ideal since it leaves some of my pre and post deploy steps to be done manually. @netlifysupport team - can you help here. It has been more than two days since the issue was posted.

same here as well… waiting for the fix…

Thanks @hrishikesh - that fixed the issue, my deploys are working again from within Github Actions. Ideally, you don’t need the CLI action Are you saying that instead of using the published netlify github action, we should just have a step like: - name: Deploy to Netlify run: | npm instal…

I have the same error on my sites… Run netlify/actions/cli@master with: args: deploy --dir=public --prod env: NETLIFY_SITE_ID: *** NETLIFY_AUTH_TOKEN: *** Does this mean the GitHub Action is not recommended any more?

Netlify-cli: ReferenceError: Response is not defined

Support

hrishikesh May 12, 2025, 6:27pm 9

Ideally, you don’t need the CLI action. You can simply install CLI as a part of your workflow. In any case, I’ve updated the action to v2.0.0: update to Node.js 22 · netlify/actions@3185065, which should resolve this.

Topic		Replies	Views
Github Action failing at "Build Netlify CLI" with node version Support deployment	25	2148	September 27, 2022
Deploy hangs on "waiting for deploy to go live" Support deployment , netlify-cli	2	1083	September 9, 2020
Nextjs github actions deployment to netlify Support building , deployment , netlify-cli , nextjs	6	1260	July 6, 2024
Cannot deploy using netlify cli in ci Support deployment , github-actions , netlify-cli , branch-deploys , environment-vars , deploy-previews	4	86	July 30, 2025
GitHub actions Nextjs deploy hangs on CDN diffing files Support deployment , github-actions , netlify-cli , nextjs	1	920	September 27, 2021

Netlify-cli: ReferenceError: Response is not defined

Related topics