📡 1.1.0

Version 1.1.0 of wrangler-action includes support for Wrangler's new API token authentication, as well as a few features requested and developed by community members using wrangler-action in their production systems.

To upgrade to wrangler-action 1.1.0, update the uses field in your workflow, passing in the new version of wrangler-action, cloudflare/wrangler-action@1.1.0:

- name: Deploy to Cloudflare Workers with Wrangler
  uses: cloudflare/wrangler-action@1.1.0

Features

Authentication via API tokens

As per cloudflare/wrangler-legacy#471, wrangler-action now supports (and encourages) the use of Cloudflare API tokens. To learn how to generate a new API token, check out our docs!

To use an API token, pass the apiToken input in your workflow to wrangler-action:

name: Deploy

on:
  push:
    branches:
      - master

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@master
      - name: Publish
        uses: cloudflare/wrangler-action@1.1.0
        with:
          apiToken: ${{ secrets.CF_API_TOKEN }}

Note that this change deprecates apiKey and email, making them optional parameters. If you use apiKey and email in your project, it will continue to work as you'd expect, but you will receive a notice in the logs that API tokens are preferred. Hooray, security!

Use a specific Wrangler version

If you need to use a specific version of Wrangler with your action, you can now pass in wranglerVersion to your workflow in order to tell NPM to install that specific version.

jobs:
  deploy:
    steps:
      uses: cloudflare/wrangler-action@1.1.0
      with:
        apiToken: ${{ secrets.CF_API_TOKEN }}
        wranglerVersion: '1.6.0'

Working directories

Per #7, wrangler-action now supports a working directory, allowing you to run wrangler-action in a specific directory in your repo. This can be useful for repositories with a Workers application that isn't the top-level of the repository:

jobs:
  deploy:
    steps:
      uses: cloudflare/wrangler-action@1.1.0
      with:
        apiToken: ${{ secrets.CF_API_TOKEN }}
        workingDirectory: 'subfoldername'

Thank you to @fshot for this contribution!

Maintenance

We've included a test directory which contains a full Workers application. We'll use this to dogfood future versions of wrangler-action and new features that we develop.

---

Thank you to the following folks for review and help on this release: @fshot, @adaptive, @EverlastingBugstopper, @minddust, @victoriabernard92

1.0.0

It's 1.0 of wrangler-action! Interested in deploying your Workers app using GitHub Actions? Check out the README to get started!

wrangler-action beta4

beta4 of wrangler-action improves the error output when your Cloudflare API key or email are missing ⚠️

wrangler-action beta3

This beta3 release updates the title/description of the action to improve SEO/discoverability

`wrangler-action` beta2

Second beta version for the initial release

• Lock down the .wrangler directory created during the Docker run of this Action (777 permissions to 770)

Wrangler-Action Beta

This is the beta for wrangler-action, which allows you to deploy Cloudflare Workers projects with GitHub Actions. Check out the README for details, and thanks for trying the project! Issues/PRs welcome :)