Repository navigation
v26.9.1
What's Changed
- feat: Always use
screenly.yml; dropscreenly_qc.ymlbranching by @salmanfarisvp in #17
Behavior change
initialize and update now always set MANIFEST_FILE_NAME=screenly.yml for both stage and production. The legacy fallback that selected screenly_qc.yml on stage when edge_app_id was empty has been removed, since it broke first-time initialize for apps that ship a single manifest.
If you still keep a separate screenly_qc.yml for stage, review before bumping your pin: move to a single screenly.yml and supply the Edge App id per environment via edge_app_id (vars.STAGE_EDGE_APP_ID / vars.PRODUCTION_EDGE_APP_ID). When edge_app_id is set it is exported as EDGE_APP_ID and takes precedence over any id in the manifest. On first-time initialize, omit it.
Usage
- uses: Screenly/edge-apps-actions/update@v26.9.1
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. Note that the legacy v1 tag is frozen and does not include this change, pin an explicit v26.9.1.
Full Changelog: v26.9.0...v26.9.1