October 26, 2026
package.json can’t be parsed, initialize and update stop with an error instead of
deploying the repo root.initialize stops if an Edge App with the same name already exists in that environment, so
running it twice can’t create 2 apps. If it can’t get the list of Edge Apps to check, it stops
without creating anything.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.
The update workflow runs 1 deploy per environment, keeps only the newest waiting run, and never cancels a deploy that's already running.
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.
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.
update stops before building when edge_app_id is empty, and both actions stop early on an empty API token or an unknown environment, with an error that names what to set.