[dependabot]

Bumps the github-actions group with 1 update: Screenly/edge-apps-actions.

Updates Screenly/edge-apps-actions from 26.9.1 to 26.10.1

Release notes

Sourced from Screenly/edge-apps-actions's releases.

v26.10.1

Call out the behaviour changes: initialize rejects some name/title characters and fails when the environment's id variable is already set, build detection now uses the build script.

What's Changed

• docs: bump README and example pins to v26.10.0 by @​salmanfarisvp in Screenly/edge-apps-actions#21
• Document publishing release notes after tagging by @​salmanfarisvp in Screenly/edge-apps-actions#22
• Document protecting production with a tag ruleset by @​salmanfarisvp in Screenly/edge-apps-actions#23
• Harden actions and examples: safe deploys, input validation, concurrency by @​salmanfarisvp in Screenly/edge-apps-actions#24

Full Changelog: Screenly/edge-apps-actions@v26.10.0...v26.10.1

v26.10.0

What's Changed

• docs: add example initialize and update workflows by @​salmanfarisvp in Screenly/edge-apps-actions#18
• fix: fail-safe edge_app_id handling and clearer setup docs by @​salmanfarisvp in Screenly/edge-apps-actions#19
• docs: deploy stage from main, production from version tags in update example by @​salmanfarisvp in Screenly/edge-apps-actions#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: Screenly/edge-apps-actions@v26.9.1...v26.10.0

Commits

• 7186950 Merge pull request #24 from Screenly/fix/harden-actions-and-examples
• 399c4bd Merge pull request #23 from Screenly/docs/tag-ruleset
• 6f4ca20 Note that production Initialize must run before restricting the environment t...
• 752ca68 Bump README and example pins to v26.10.1
• ae0b2f2 Rename README heading to Edge Apps GitHub Actions and expand intro
• fd24774 Keep repo internals out of deploys, guard initialize, stage from default bran...
• 55fbac0 added tag badge
• 1715166 Harden actions and examples: input validation, concurrency, permissions
• 7a040da Document protecting production with a v* tag ruleset
• e9fa643 Merge pull request #22 from Screenly/docs/release-notes
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml