{"product":"cli","releases":[{"date":"2026-08-28","entries":[{"areas":["developers"],"breaking":false,"content_html":"\u003cp\u003eThe settings you write in \u003ccode\u003escreenly.yml\u003c/code\u003e now appear to whoever installs your app in the order you\nwrote them. \u003ccode\u003escreenly edge-app deploy\u003c/code\u003e works out each setting\u0026rsquo;s position from where it sits in the\nmanifest and sends that along.\u003c/p\u003e\n\u003cp\u003eThis matters because a settings form is a form. An address above a postcode, a start time above an\nend time, credentials grouped together: you already put them in a sensible order when you wrote\nthem, and until now that order was not carried anywhere.\u003c/p\u003e\n\u003cp\u003eSet \u003ccode\u003edisplay_order\u003c/code\u003e on a setting to override the position it would get. An order you write by hand\nis never overwritten, and \u003ccode\u003edeploy\u003c/code\u003e sends the computed order without rewriting your manifest, so\nnothing appears in your working tree after a deploy.\u003c/p\u003e\n\u003cp\u003eSecrets are left out of the automatic ordering unless you give them a descriptor of their own,\nwhich keeps the password field behaving the way it does today.\u003c/p\u003e\n","description":"Settings used to render in whatever order the backend returned; deploy now assigns each one a position from where it sits in your manifest.","title":"Edge App settings appear in the order you declared them","type":"improvement","url":"https://www.screenly.io/releases/cli/26.8.0/edge-app-settings-order/"},{"areas":["developers"],"breaking":false,"content_html":"\u003cp\u003eCLI releases are numbered by year and month now, so this one is 26.8.0 rather than the 1.2.3 it\nwould otherwise have been. That is the same scheme Screenly and ScreenlyOS use, which makes it\npossible to tell at a glance whether the CLI you are running is from the same era as the platform\nit is talking to.\u003c/p\u003e\n\u003cp\u003eNothing about the CLI\u0026rsquo;s behavior changes with the numbering, and a version you have already pinned\nkeeps resolving to exactly what it did before.\u003c/p\u003e\n\u003cblockquote\u003e\n\u003cp\u003e\u003cstrong\u003eIf you pin a version in CI:\u003c/strong\u003e a range like \u003ccode\u003e1.x\u003c/code\u003e or \u003ccode\u003e^1.2\u003c/code\u003e will never match a release again.\nPoint it at \u003ccode\u003e26.8.0\u003c/code\u003e or later, or at the latest release, depending on how tightly you want to\npin. The GitHub Action\u0026rsquo;s default was updated at the same time.\u003c/p\u003e\n\u003c/blockquote\u003e\n","description":"Releases jumped from 1.2.2 to 26.8.0 and are now named by year and month, matching the rest of Screenly.","title":"The CLI version numbers moved to CalVer","type":"improvement","url":"https://www.screenly.io/releases/cli/26.8.0/calver-version-numbers/"}],"json":"https://www.screenly.io/releases/cli/26.8.0/v1.json","product":"cli","product_label":"Screenly CLI","url":"https://www.screenly.io/releases/cli/26.8.0/","version":"26.8.0"}],"title":"Screenly CLI 26.8.0","url":"https://www.screenly.io/releases/cli/26.8.0/","version":1}