Screenly CLI 26.8.0: Edge App settings appear in the order you declared them

Fri, 28 Aug 2026 00:00:00 +0000

The settings you write in screenly.yml now appear to whoever installs your app in the order you wrote them. screenly edge-app deploy works out each setting’s position from where it sits in the manifest and sends that along.

This matters because a settings form is a form. An address above a postcode, a start time above an end time, credentials grouped together: you already put them in a sensible order when you wrote them, and until now that order was not carried anywhere.

Set display_order on a setting to override the position it would get. An order you write by hand is never overwritten, and deploy sends the computed order without rewriting your manifest, so nothing appears in your working tree after a deploy.

Secrets are left out of the automatic ordering unless you give them a descriptor of their own, which keeps the password field behaving the way it does today.

Screenly CLI 26.8.0: The CLI version numbers moved to CalVer

Fri, 28 Aug 2026 00:00:00 +0000

CLI releases are numbered by year and month now, so this one is 26.8.0 rather than the 1.2.3 it would otherwise have been. That is the same scheme Screenly and ScreenlyOS use, which makes it possible to tell at a glance whether the CLI you are running is from the same era as the platform it is talking to.

Nothing about the CLI’s behavior changes with the numbering, and a version you have already pinned keeps resolving to exactly what it did before.

If you pin a version in CI: a range like 1.x or ^1.2 will never match a release again. Point it at 26.8.0 or later, or at the latest release, depending on how tightly you want to pin. The GitHub Action’s default was updated at the same time.

Screenly CLI 26.8.0 | Screenly

Screenly CLI 26.8.0: Edge App settings appear in the order you declared them

Screenly CLI 26.8.0: The CLI version numbers moved to CalVer