v26.10.0

What's Changed

• docs: add example initialize and update workflows by @salmanfarisvp in #18
• fix: fail-safe edge_app_id handling and clearer setup docs by @salmanfarisvp in #19
• docs: deploy stage from main, production from version tags in update example by @salmanfarisvp in #20

Behavior change

initialize and update now fail closed on bad inputs instead of continuing:

• An empty screenly_api_token fails immediately with a message to add the SCREENLY_API_TOKEN secret for that environment.
• environment must be exactly stage or production; anything else fails.
• update requires a real edge_app_id. Empty values and placeholders left by bad expressions (false, true, null, none, 0, undefined) fail with a message pointing at STAGE_EDGE_APP_ID / PRODUCTION_EDGE_APP_ID.
• initialize treats those same placeholders as unset, so a first-time create is not sent a bogus id.

Review before bumping your pin: make sure each environment has SCREENLY_API_TOKEN and that update jobs pass the matching repo variable.

Example workflows

examples/update-edge-app.yml now deploys stage on every push to the default branch (rolling) and production when a version tag like v26.10.0 is pushed. The production job skips tag deletions and refuses tags whose commit is not on the default branch. Copy it into your app repo to adopt the same release flow.

Usage

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

Requires screenly/cli v26.9.0 or later. The legacy v1 tag is frozen and does not include this change; pin an explicit v26.10.0.

Full Changelog: v26.9.1...v26.10.0