update-latest

Overview ¶

Command update-latest points latest/COMMIT in encore-releases2 at the commit whose build was just finalized, so tooling can find the newest build of main without knowing its sha: read latest/COMMIT, then fetch latest/<sha>/encore-<os>_<arch>.tar.gz.

It only ever writes the pointer for a build stored under latest/<commit>, and refuses any other prefix, so a proper release can't end up behind it. Runs of the workflow are serialized by its concurrency group, so on push the pointer advances in commit order; re-running an older run's finalize job moves it back to that (complete) build until the next push.

Configuration (environment variables):

R_COMMIT             the commit sha this build was made from
R_VERSION            release version, e.g. "v0.0.0-develop+<commit>"
R_RELEASE_PREFIX     object prefix in the bucket; must be "latest/<commit>"
RUNNER_TEMP          scratch directory