Pull requests: a deploy-plan check, preview environments and deploy tokens for CI
A pull request into a branch an app's environment follows now gets a check on its head commit saying what deploying it would do to production: the files it changes, each model change and how many of production's records it reaches. A removed field still holding values, a new type some values can't take, or a new required or unique rule existing records break fails the check, so it shows before the merge. Web apps can also turn on preview environments: each pull request gets pr-<number>, following its branch, with its address on the pull request, deleted at merge or close.
Both are under Pull requests on Settings → Git. The check can only warn instead of failing. A preview's records start empty or as a copy of production's with personal fields anonymized, up to five are open at once, and pull requests from forks don't get one.
For teams that keep their own CI, deploy tokens reach one development environment: Push changes its files, and Push and deploy also deploys production from it. With @inferencebureau/apps 0.10.0, ib-apps push --app <slug> --env <environment> in a fresh checkout sends what the folder has, so a GitHub Actions workflow can push and deploy without anyone's sign-in. Settings → Git shows the workflow when you create a token.
More in Pull requests.