# Deploy from GitHub Actions with the Deploy to Evolving Edge CDN Action

> A GitHub Action, Deploy to Evolving Edge CDN, runs ee-cdn-cli in any workflow, including Hugo, Jekyll and Zola sites that don't use Node. Its inputs match the CLI's options. Pin an exact release, because the step holds your deploy token.

Date: October 29, 2026 · Type: Added · Products: CLI

Source: https://changelog.evolvingedge.ai/2026/10/github-action-deploy/

If your site is built in GitHub Actions, you can now deploy it to Evolving Edge with one step, whatever built it. The Deploy to Evolving Edge Action, listed on GitHub Marketplace, runs `ee-cdn-cli` with its own copy of Node, so it works for sites built with Hugo, Jekyll, Zola and other tools that don't use Node. Its inputs match the CLI's options, including the [image options from 0.4.0](https://changelog.evolvingedge.ai/2026/10/cli-image-conversion/).

```yaml
- uses: evolving-edge/deploy-action@v1.0.1
```

The [Action's README](https://github.com/evolving-edge/deploy-action) lists every input.

## Pin an exact release

The step holds your deploy token, so choose exactly what it runs.

- **Use an exact release, such as `@v1.0.1`, or a commit SHA.** Never use `@main`.
- **`@v1` picks up every new release automatically**, and with it whichever version of `ee-cdn-cli` that release runs. Each release's notes name the CLI version it runs. v1.0.1 runs `ee-cdn-cli` 0.4.1.
- **Pin `builder-version` too**, so the packaging tool the CLI downloads is the same on every run.

## If you already use the Action from ee-cdn-cli

Workflows that use `evolving-edge/ee-cdn-cli@v0.4.0` keep working. To move to the new Action, change the `uses:` line.

## Limits

- **It deploys Level 0 and Level 2 sites.** Level 1 sites are refused.

## What you need to do

Nothing, unless you want to deploy from GitHub Actions. To start, add the step to your workflow, pinned to an exact release. If you use `evolving-edge/ee-cdn-cli@v0.4.0`, change its `uses:` line to `evolving-edge/deploy-action@v1.0.1`.