0015: Direct-to-develop workflow
Maintainers and agents commit straight to develop instead of opening one branch and pull request per change.
0017: Toolchain exceptions to the repo standard
The classic TypeScript alias, the default checker count, and the standard toolchain items we hold back until upstream catches up.
0015: Direct-to-develop workflow
Maintainers and agents commit straight to develop instead of opening one branch and pull request per change.
0017: Toolchain exceptions to the repo standard
The classic TypeScript alias, the default checker count, and the standard toolchain items we hold back until upstream catches up.
GitHub Actions builds skip the Turbopack build cache, because a cold SaaS build with it runs the 7 GB runner out of memory.
The repo standard restores .next/cache in every job that runs next build, so the Turbopack build cache (turbopackFileSystemCacheForBuild, on by default since Next.js 16.3) survives between runs. The repo is private, so CI runs on standard runners with 2 vCPU, about 7.9 GB of RAM, a 4 GB swap file and about 10 GB of free disk. Larger runners are out of scope.
We turned the cache on in CI in pull request 96, still building Next apps one at a time (--concurrency=1). Three cold saas builds failed with "The runner has received a shutdown signal". A background step that logged memory every 15 seconds showed RAM at 7.8 of 7.9 GB and swap at 3 GB within three minutes of the build starting, followed by the shutdown. Disk stayed at about 62 of 73 GB used. The same cold build without the cache finishes on this runner in about 15 minutes.
A larger swap file does not fit: the free disk also has to hold the build outputs and the cache itself, and a 16 GB swap file filled the disk before the build started.
turbopackFileSystemCacheForBuild stays on for local and Vercel builds and is off when GITHUB_ACTIONS is true. GITHUB_ACTIONS is in globalPassThroughEnv, so CI still shares the Turbo Remote Cache with local and Vercel builds. CI has no .next/cache restore or save step, because nothing writes that cache there. The Build job keeps a background step that logs memory and disk usage.
saas costs a full cold build in CI (about 15 minutes). The Turbo Remote Cache still skips the build entirely when the app's inputs are unchanged.apps/*/.next/cache in the Build job (save only on develop), and measure again with the memory log.Last updated on
0015: Direct-to-develop workflow
Maintainers and agents commit straight to develop instead of opening one branch and pull request per change.
0017: Toolchain exceptions to the repo standard
The classic TypeScript alias, the default checker count, and the standard toolchain items we hold back until upstream catches up.