26.10.2
- New Developers
Checks, initialize, and update now come as reusable workflows
Reusable checks, initialize, and update workflows hold the whole deploy setup, so an Edge App repo's workflow files only pin a version and pass SCREENLY_API_TOKEN.
- Improvement Developers
Deploys to an environment run one at a time
The update workflow runs 1 deploy per environment, keeps only the newest waiting run, and never cancels a deploy that's already running.
- Fixes and improvements
The initialize action won't create the same app twice, and other fixes
initialize stops if an Edge App with the same name already exists, and both actions stop with an error when package.json can't be parsed.
26.10.1
- Improvement Developers Breaking change
Initialize runs once per environment and shows the new id right away
initialize stops when the environment's id variable is already set, and puts the new Edge App's id in the job summary as soon as the app is created.
- Fixes and improvements
Any app with a build script is built and deployed from dist
initialize and update build any app whose package.json has a build script and deploy it from dist/, whether or not it uses the Edge Apps library.
26.10.0
26.9.1
26.9.0
- New Developers
Each environment's Edge App id comes from a repository variable
initialize and update take an edge_app_id input, so stage and production can share 1 screenly.yml and keep their ids in repository variables.
- Improvement Developers
The actions' version numbers moved to CalVer
Releases jumped from 1.3.0 to 26.9.0 and are now named by year and month, and the v1 tag stays where it is.
- Fixes and improvements
Builds work with the Edge Apps library in dependencies, and other improvements
initialize and update build your app when @screenly/edge-apps is listed under dependencies, and run a fixed CLI version so a new CLI release can't change your deploys.