Request: Install Newer Version of Wrangler by Default

[CNX-Inc]

Noting, this might be something with my project (I'm not much of a node user but i have updated my package.json and package-lock.json files to no avail.

It seems as though the action installs an outdated wrangler by default, from my logs:
/usr/local/bin/npm i wrangler@3.90.0

Currently I'm using Wrangler 4.14.1 (locally) and the older version seems to not like to deploy.

Here's how I've worked around the issue, but thought you all might want to update the default or maybe provide an version: 4.14.1 option to with:

Thanks!

  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v4
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          workingDirectory: "data-worker"
          preCommands: |
            echo "*** pre commands ***"
            echo `pwd`
            npx wrangler --version
            npm install wrangler@latest
            echo "******"

[mamiu]

Had the same problem right now when trying to use the IMAGES binding.

[RobFaustLZ]

Following. All the Wrangler project initialization scripts have been updated to use .jsonc config files by default rather than the old .toml format. But, .jsonc isn't supported until Wrangler 3.91 and the default is currently set to 3.90.

[omkhar]

I presume there is a valid reason for not changing default behavior. Rather than invoking a manual installation, you can just pass wranglerVersion like this:

     - uses: actions/checkout@v4
      - uses: cloudflare/wrangler-action@v3
        name: Deploy to Cloudflare (Production)
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          wranglerVersion: "latest"

[CNX-Inc]

@omkhar - are you suggesting wranglerVersion: "latest" will install the latest? (vs. my hack install)?

That seems cleaner for sure.

[stof]

An alternative is to add a step running npm ci before the step using cloudflare/wrangler-action, to install the npm dependencies of the project. In such case, cloudflare/wrangler-action will use the version of wrangler installed in your project.

[ckenna]

This is a pretty bad issue that almost caused an outage while I was working on some CI/CD GitHub actions.

Fortunately, we caught it in a test environment.

Here's the problem with the old Wrangler version: It is apparently so old that it won't even update our Secrets Store secrets or our Secret bindings. Worse: It won't warn about this either because I guess how could it know?

So it happily deleted Secrets Store bindings we had in place from Wrangler 4.

Comparing old version output:

⛅️ wrangler 3.90.0 (update available 4.27.0)
  ---------------------------------------------

  ▲ [WARNING] The version of Wrangler you are using is now out-of-date.

    Please update to the latest version to prevent critical errors.
    Run `npm install --save-dev wrangler@4` to update to the latest version.
    After installation, run Wrangler with `npx wrangler`.

  Total Upload: 68.96 KiB / gzip: 15.04 KiB
  Worker Startup Time: 16 ms
  Your worker has access to the following bindings:
  - Durable Objects:
    - R2_LOADER_OBJECT: R2Loader
  - R2 Buckets:
    - IMAGES_BUCKET: blah-blah-images-stage
  - Vars:
    - S3_BUCKET: "blah-blah-images-staging"
  Uploaded staging-blah-blah-registry (3.13 sec)
  Worker Version ID: 9aaa95b3-7ce9-4664-a13a-a9b6f4dfd8e6

To new:

/usr/local/bin/npx wrangler versions upload --tag v0.0.8 --env stage
   ⛅️ wrangler 4.27.0
  ───────────────────
  Total Upload: 60.77 KiB / gzip: 13.66 KiB
  Worker Startup Time: 13 ms
  Your Worker has access to the following bindings:
  Binding                                                                                 Resource
  env.R2_LOADER_OBJECT (R2Loader)                                                         Durable Object
  env.IMAGES_BUCKET (blah-lbah-images-stage)                                                 R2 Bucket
  env.AWS_ACCESS_KEY_ID (461efae16d334483804e5d1709f34fa5/STAGE_AWS_ACCESS_KEY)           Secrets Store Secret
  env.AWS_SECRET_ACCESS_KEY (461efae16d334483804e5d1709f34fa5/STAGE_AWS_SECRET_KEY)       Secrets Store Secret
  env.SIGNING_KEY (461efae16d334483804e5d1709f34fa5/STAGE_SIGNING_KEY)                    Secrets Store Secret
  env.NEW_SIGNING_KEY (461efae16d334483804e5d1709f34fa5/STAGE_NEW_SIGNING_KEY)            Secrets Store Secret
  env.S3_BUCKET ("blah-blah-images-staging")                                                 Environment Variable
  Uploaded staging-blah-blah-registry (1.75 sec)
  Worker Version ID: 613a4e31-bf88-4edc-9d4e-27456d204b0a