Runtime changelog, 31 October 2026

What shipped in Runtime Cloud on 31 October 2026: CI/CD setup can be a list of layers; and CI/CD: checks a release waits on get machines first.

CI/CD setup can be a list of layers

setup: in runtime.yml now also accepts a list of up to 16 commands, run in order. A push to the production branch keeps each finished layer as a snapshot, keyed to that layer, the layers before it, the machine size and the cache files. A later setup starts from the deepest layer that is ready and runs only the layers after it, so a change to the last layer does not run the earlier ones again, and a setup that is stopped or fails partway keeps the layers it finished. Pull request checks start from these snapshots but never write them. A setup: of one command works as before.

CI/CD: checks a release waits on get machines first

When an account's checks are short of machines, a pull request from the repository's own branches into the production branch gets them first, then a push to the production branch, each oldest first, then every other check. While one of these waits, the account's lower checks hand it machines as their running tasks end. A pull request from a fork is ordered with every other check. To skip pull requests into a branch whose commits are tested another way, such as a staging branch, list the branches to check in the production branch's config: pull_requests: { branches: [main] }.