Edge Apps GitHub Actions 26.9.0 | Screenly

Edge Apps GitHub Actions 26.9.0: Each environment's Edge App id comes from a repository variable

Tue, 08 Sep 2026 00:00:00 +0000

An Edge App that runs in stage and production has 2 ids, and until now each one lived in its own manifest: screenly_qc.yml for stage and screenly.yml for production. A setting added to one file had to be added to the other.

With the new edge_app_id input, the id comes from the workflow instead. Keep each environment’s id in a repository variable and pass the matching one:

- uses: Screenly/edge-apps-actions/update@v26.9.0
 with:
 screenly_api_token: ${{ secrets.SCREENLY_API_TOKEN }}
 environment: stage
 edge_app_id: ${{ vars.STAGE_EDGE_APP_ID }}

When edge_app_id is set, the action reads screenly.yml in both environments, and the id you pass wins over any id in the manifest. So 1 manifest serves stage and production, and only the variable changes between them.

Leave it out and nothing changes: stage still reads screenly_qc.yml, and production reads screenly.yml, each with its own id.

Edge Apps GitHub Actions 26.9.0: The actions' version numbers moved to CalVer

Tue, 08 Sep 2026 00:00:00 +0000

Releases of the Edge Apps GitHub Actions are numbered by year and month now, so the release after 1.3.0 is 26.9.0. That’s the same scheme Screenly, ScreenlyOS, the CLI, and the Edge Apps library use.

Each release is 1 fixed tag, such as v26.9.0, and there’s no moving tag that follows the latest release. v1 stays on 1.3.0 for good. A workflow that uses @v1 keeps running exactly what it ran before, and it won’t get anything released from here on.

Nothing about the actions’ behavior changes with the numbering.

If this affects you: a workflow that uses @v1 won’t pick up new releases. Replace @v1 with an exact tag, such as Screenly/edge-apps-actions/update@v26.9.0, and bump it when you want a newer release. Dependabot’s github-actions updates can open those bumps for you.

Edge Apps GitHub Actions 26.9.0: Builds work with the Edge Apps library in dependencies, and other improvements

Tue, 08 Sep 2026 00:00:00 +0000

Fixes

initialize and update build your app when @screenly/edge-apps is listed under dependencies, not only under devDependencies.

Improvements

initialize and update run Screenly CLI 26.9.0 instead of whichever CLI release is newest, so a new CLI release doesn’t change how your app deploys until you move to a newer version of the actions.