Free Screenly Player with every Business or Enterprise yearly plan. How it works →

April 22, 2026

A new update action deploys an existing Edge App

Edge Apps GitHub Actions New Developers

Once initialize has created an Edge App, the update action ships each new version of it. Put it in a workflow that runs on push, and every merge reaches Screenly without anyone running the CLI by hand:

- uses: Screenly/edge-apps-actions/update@v1
  with:
    screenly_api_token: ${{ secrets.SCREENLY_API_TOKEN }}
    environment: stage # optional, defaults to stage

It builds the same way initialize does. If package.json lists @screenly/edge-apps under devDependencies, it installs with Bun, runs bun run build, and deploys dist/. Otherwise it deploys the repo root as it is.

The app it deploys to is the one whose id is in the manifest: screenly_qc.yml for stage and screenly.yml for production.

Latest releases

All Edge Apps GitHub Actions releases →

New Developers
Checks, initialize, and update now come as reusable workflows
Reusable checks, initialize, and update workflows hold the whole deploy setup, so an Edge App repo's workflow files only pin a version and pass SCREENLY_API_TOKEN.
Improvement Developers
Deploys to an environment run one at a time
The update workflow runs 1 deploy per environment, keeps only the newest waiting run, and never cancels a deploy that's already running.
Fixes and improvements
The initialize action won't create the same app twice, and other fixes
initialize stops if an Edge App with the same name already exists, and both actions stop with an error when package.json can't be parsed.
Improvement Developers Breaking change
Initialize runs once per environment and shows the new id right away
initialize stops when the environment's id variable is already set, and puts the new Edge App's id in the job summary as soon as the app is created.
Fixes and improvements
Any app with a build script is built and deployed from dist
initialize and update build any app whose package.json has a build script and deploy it from dist/, whether or not it uses the Edge Apps library.

Latest releases

Checks, initialize, and update now come as reusable workflows

Deploys to an environment run one at a time

The initialize action won't create the same app twice, and other fixes

Initialize runs once per environment and shows the new id right away

Any app with a build script is built and deployed from dist