Are you running a globally installed version of Wrangler instead of the one in your project, perhaps

J

James•4/8/25, 5:32 PM

Is this using

wrangler-action

wrangler-action

wrangler-action

wrangler-action? Are you pinning your

wranglerVersion

wranglerVersion

wranglerVersion

wranglerVersion there in your Actions config?

J

James•4/8/25, 5:32 PM

Or using an old

wrangler-action

wrangler-action

wrangler-action

wrangler-action version that used to pin to a specific version?

M

Mitya•4/8/25, 5:33 PM

I'm really not sure, this is a bit beyond me. I am using the Action, yes, but I'm no expert on it.

M

Mitya•4/8/25, 5:33 PM

Happy to check anything and reply with findings.

SSouthpaw Are you running a globally installed version of Wrangler instead of the one in y...

M

Mitya•4/8/25, 5:33 PM

This is being run within GH

J

James•4/8/25, 5:33 PM

Can you share your config for the wrangler-action Github action? It'll be in

.github/workflows/<something>.yml

.github/workflows/<something>.yml

.github/workflows/<something>.yml

.github/workflows/<something>.yml. You likely are using an old version of

wrangler-action

wrangler-action

wrangler-action

wrangler-action, or have

wranglerVersion

wranglerVersion

wranglerVersion

wranglerVersion pinned in it

M

Mitya•4/8/25, 5:33 PM

Sure, sec

J

James•4/8/25, 5:34 PM

(double check it doesn't have any secrets in it. It shouldn't, but do be wary)

M

Mitya•4/8/25, 5:34 PM

name: Deploy

on:
  push:
    branches:
      - main
      - stage

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'prod' || 'stage' }}
          apiToken: ${{ secrets.CF_API_TOKEN }}
          secrets: |
            REDACTED
        env:
            REDACTED: ${{ secrets.REDACTED }}

name: Deploy

on:
  push:
    branches:
      - main
      - stage

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'prod' || 'stage' }}
          apiToken: ${{ secrets.CF_API_TOKEN }}
          secrets: |
            REDACTED
        env:
            REDACTED: ${{ secrets.REDACTED }}

name: Deploy

on:
  push:
    branches:
      - main
      - stage

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'prod' || 'stage' }}
          apiToken: ${{ secrets.CF_API_TOKEN }}
          secrets: |
            REDACTED
        env:
            REDACTED: ${{ secrets.REDACTED }}

name: Deploy

on:
  push:
    branches:
      - main
      - stage

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'prod' || 'stage' }}
          apiToken: ${{ secrets.CF_API_TOKEN }}
          secrets: |
            REDACTED
        env:
            REDACTED: ${{ secrets.REDACTED }}

M

Mitya•4/8/25, 5:34 PM

Appreciate the help BTW

J

James•4/8/25, 5:35 PM

Hmm, that looks fine

M

Mitya•4/8/25, 5:35 PM

I did do a messy merge with lots of conflicts today. One branch was still using TOML, the other branch JSON. Could be related.

M

Mitya•4/8/25, 5:35 PM

Just not sure how.

M

Mitya•4/8/25, 5:36 PM

Pehraps as @petebd says I'll run

npm i

npm i

npm i

npm i afresh to see if that flushes things

P

petebd•4/8/25, 5:36 PM

The command you are using is

npx wrangler secret bulk --env stage

npx wrangler secret bulk --env stage

npx wrangler secret bulk --env stage

npx wrangler secret bulk --env stage. Are you running this locally or is it running in the Github action?

M

Mitya•4/8/25, 5:38 PM

GH action. When I test locally I run:

wrangler dev --config \"dev.json\" --remote --port 1933 --env dev --test-scheduled

wrangler dev --config \"dev.json\" --remote --port 1933 --env dev --test-scheduled

wrangler dev --config \"dev.json\" --remote --port 1933 --env dev --test-scheduled

wrangler dev --config \"dev.json\" --remote --port 1933 --env dev --test-scheduled

M

Mitya•4/8/25, 5:38 PM

Ran

npm i

npm i

npm i

npm i

no changes resulted.

M

Mitya•4/8/25, 5:40 PM

Still failing to build - exact same errors (can't find the env; worker must have a name, etc.)

J

James•4/8/25, 5:41 PM

Can you share the full actions log? I'm confused as to why it's using an old wrangler version

M

Mitya•4/8/25, 5:42 PM

Likewise. Where do I find that? It says it's saved the log to

/usr/...

/usr/...

/usr/...

/usr/..., but I'm not sure where that is.

M

Mitya•4/8/25, 5:42 PM

Should that be in the GH repo?

J

James•4/8/25, 5:42 PM

In the Actions run on your GH repo, you should be able to open the run and then hit the cog in the top right and view the raw logs / download them: https://i.james.pub/file/2025/04/77a60be7-4c25-4cc1-acb0-1cfb30a7dd96.png

M

Mitya•4/8/25, 5:43 PM

Got it

message.txt39.82KB

J

James•4/8/25, 5:43 PM

2025-04-08T17:39:23.4216882Z [command]/usr/local/bin/npx --no-install wrangler --version
2025-04-08T17:39:28.4759522Z npm error npx canceled due to missing packages and no YES option: ["wrangler@4.9.0"]
2025-04-08T17:39:28.4767790Z npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-04-08T17_39_23_900Z-debug-0.log
2025-04-08T17:39:28.4895211Z ⚠️ Wrangler not found or version is incompatible. Installing...

2025-04-08T17:39:23.4216882Z [command]/usr/local/bin/npx --no-install wrangler --version
2025-04-08T17:39:28.4759522Z npm error npx canceled due to missing packages and no YES option: ["wrangler@4.9.0"]
2025-04-08T17:39:28.4767790Z npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-04-08T17_39_23_900Z-debug-0.log
2025-04-08T17:39:28.4895211Z ⚠️ Wrangler not found or version is incompatible. Installing...

2025-04-08T17:39:23.4216882Z [command]/usr/local/bin/npx --no-install wrangler --version
2025-04-08T17:39:28.4759522Z npm error npx canceled due to missing packages and no YES option: ["wrangler@4.9.0"]
2025-04-08T17:39:28.4767790Z npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-04-08T17_39_23_900Z-debug-0.log
2025-04-08T17:39:28.4895211Z ⚠️ Wrangler not found or version is incompatible. Installing...

2025-04-08T17:39:23.4216882Z [command]/usr/local/bin/npx --no-install wrangler --version
2025-04-08T17:39:28.4759522Z npm error npx canceled due to missing packages and no YES option: ["wrangler@4.9.0"]
2025-04-08T17:39:28.4767790Z npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-04-08T17_39_23_900Z-debug-0.log
2025-04-08T17:39:28.4895211Z ⚠️ Wrangler not found or version is incompatible. Installing...

J

James•4/8/25, 5:43 PM

Okay I see what's happening

M

Mitya•4/8/25, 5:45 PM

Hmm, not sure I understand that. I have Wrangler specified in my

package.json

package.json

?

J

James•4/8/25, 5:46 PM

It seems the way wrangler-action seems to check if wrangler is installed is by

npx --no-install

npx --no-install

npx --no-install

npx --no-install. Because you're not running a package manager install before the action, it's not seeing one as installed. So then it defaults to installing, and the default is 3.90.0: https://github.com/cloudflare/wrangler-action/blob/707f63750981584eb6abc365a50d441516fb04b8/src/index.ts#L8

M

Mitya•4/8/25, 5:47 PM

Oh. Why would this have started happening just by switching from TOML to JSON? This always deployed fine before.

J

James•4/8/25, 5:47 PM

Because JSON wasn't supported by default in 3.90.0

M

Mitya•4/8/25, 5:47 PM

Riiiiiight.

J

James•4/8/25, 5:48 PM

If you update your action to something like this:

name: Deploy

on:
  push:
    branches:
      - main
      - stage

env:
  NODE_VERSION: 22.x

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: ${{ env.NODE_VERSION }}
      - run: npm ci

      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'prod' || 'stage' }}
          apiToken: ${{ secrets.CF_API_TOKEN }}
          secrets: |
            REDACTED
        env:
            REDACTED: ${{ secrets.REDACTED }}

name: Deploy

on:
  push:
    branches:
      - main
      - stage

env:
  NODE_VERSION: 22.x

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: ${{ env.NODE_VERSION }}
      - run: npm ci

      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'prod' || 'stage' }}
          apiToken: ${{ secrets.CF_API_TOKEN }}
          secrets: |
            REDACTED
        env:
            REDACTED: ${{ secrets.REDACTED }}

name: Deploy

on:
  push:
    branches:
      - main
      - stage

env:
  NODE_VERSION: 22.x

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: ${{ env.NODE_VERSION }}
      - run: npm ci

      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'prod' || 'stage' }}
          apiToken: ${{ secrets.CF_API_TOKEN }}
          secrets: |
            REDACTED
        env:
            REDACTED: ${{ secrets.REDACTED }}

name: Deploy

on:
  push:
    branches:
      - main
      - stage

env:
  NODE_VERSION: 22.x

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: ${{ env.NODE_VERSION }}
      - run: npm ci

      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'prod' || 'stage' }}
          apiToken: ${{ secrets.CF_API_TOKEN }}
          secrets: |
            REDACTED
        env:
            REDACTED: ${{ secrets.REDACTED }}

It should resolve it and let you use JSON.

J

James•4/8/25, 5:48 PM

Note the addition of the

setup-node

setup-node

setup-node

setup-node step before the deploy action, and then the

npm ci

npm ci

npm ci

npm ci, which'll run an install from your own

package.json

package.json

```
package-lock.json
```
```
package-lock.json
```
, so that'll have your pinned new wrangler version

J

James•4/8/25, 5:49 PM

wrangler-action

wrangler-action

wrangler-action

wrangler-action will then see this as installed and use that version

M

Mitya•4/8/25, 5:49 PM

Nice one, thank you. Sec, I'll just to try to implement that in my current file and report back.

M

Mitya•4/8/25, 5:51 PM

Is the

NODE_VERSION

NODE_VERSION

NODE_VERSION

NODE_VERSION part necessary? Doesn't that get implied via the Wrangler

compatibility_date

compatibility_date

compatibility_date

compatibility_date flag?

M

Mitya•4/8/25, 5:51 PM

I'm just wary of adding this if I didn't have it before, and suddenly my Worker runs on a new version of Node that's untested for us

J

James•4/8/25, 5:52 PM

I added that solely for the

node-version: ${{ env.NODE_VERSION }}

node-version: ${{ env.NODE_VERSION }}

node-version: ${{ env.NODE_VERSION }}

node-version: ${{ env.NODE_VERSION }} config in the

setup-node

setup-node

setup-node

setup-node step

J

James•4/8/25, 5:52 PM

It's not just used Workers at all

J

James•4/8/25, 5:52 PM

It's just a pattern I personally do so I can easily config things. You could just as easily replace that line with

node-version: 22

node-version: 22

node-version: 22

node-version: 22

J

James•4/8/25, 5:52 PM

This is just the version that's installed in the Action for the

npm ci

npm ci

npm ci

npm ci command

J

James•4/8/25, 5:53 PM

I'd match that with whatever version you're running locally if that's working fine for you

M

Mitya•4/8/25, 5:53 PM

Ooh, not for the Worker runtime

J

James•4/8/25, 5:53 PM

Yeah this is purely for the GitHub action

M

Mitya•4/8/25, 5:53 PM

Got it

M

Mitya•4/8/25, 5:54 PM

OK here's my updated file:

name: Deploy

on:
  push:
    branches:
      - main
      - stage

env:
  NODE_VERSION: 22

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
          with:
            node-version: ${{ env.NODE_VERSION }}
      - run: npm ci
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'prod' || 'stage' }}
          apiToken: ${{ secrets.CF_API_TOKEN }}
          secrets: |
            REDACTED
        env:
            REDACTED: ${{ secrets.REDACTED }}

name: Deploy

on:
  push:
    branches:
      - main
      - stage

env:
  NODE_VERSION: 22

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
          with:
            node-version: ${{ env.NODE_VERSION }}
      - run: npm ci
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'prod' || 'stage' }}
          apiToken: ${{ secrets.CF_API_TOKEN }}
          secrets: |
            REDACTED
        env:
            REDACTED: ${{ secrets.REDACTED }}

name: Deploy

on:
  push:
    branches:
      - main
      - stage

env:
  NODE_VERSION: 22

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
          with:
            node-version: ${{ env.NODE_VERSION }}
      - run: npm ci
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'prod' || 'stage' }}
          apiToken: ${{ secrets.CF_API_TOKEN }}
          secrets: |
            REDACTED
        env:
            REDACTED: ${{ secrets.REDACTED }}

name: Deploy

on:
  push:
    branches:
      - main
      - stage

env:
  NODE_VERSION: 22

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
          with:
            node-version: ${{ env.NODE_VERSION }}
      - run: npm ci
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'prod' || 'stage' }}
          apiToken: ${{ secrets.CF_API_TOKEN }}
          secrets: |
            REDACTED
        env:
            REDACTED: ${{ secrets.REDACTED }}

M

Mitya•4/8/25, 5:54 PM

That look OK?

J

James•4/8/25, 5:55 PM

The spacing with the

with

with

under the

uses: actions/setup-node@v4

uses: actions/setup-node@v4

uses: actions/setup-node@v4

uses: actions/setup-node@v4 looks a bit off. It should be inline with the

uses

uses

J

James•4/8/25, 5:55 PM

Throw it into a YAML validator to test basic things like that

M

Mitya•4/8/25, 5:57 PM

This feels a good time for a 2-spaces vs. 4-spaces flame war!

M

Mitya•4/8/25, 5:57 PM

OK that was the only thing - passed the linter otherwise

Are you running a globally installed version of Wrangler instead of the one in your project, perhaps

Similar Threads

Similar Threads

Similar Threads