Persist .next/cache across deploys for faster rebuilds
Deploy / release (push) Skipped
Deploy / deploy (push) Successful in 2m2s

Each deploy creates a fresh worktree and deletes .next, losing the
Turbopack build cache. Now restore .next/cache from the live site
into the stage before pnpm build, so Next.js can do incremental
compilation. After cutover the cache persists in the live .next/ for
the next deploy.
This commit is contained in:
openhands committed 2026-07-23 19:33:12 +02:00
1 parent 7dbca4117c
commit dae381e07c
1 file changed
+7
+7
View File
@@ -299,6 +299,13 @@ jobs:
find . -maxdepth 3 -name '*.tsbuildinfo' -delete 2>/dev/null || true
rm -rf .output dist .next .next/types .next/dev
# Restore build cache from last deploy so Turbopack can do
# incremental compilation (much faster rebuilds).
if [ -d "${LIVE}/.next/cache" ]; then
mkdir -p .next/cache
cp -r "${LIVE}/.next/cache/." .next/cache/
fi
# Stage shares MySQL with the live app + emulator. Keep the stage pool
# tiny so install/test/build cannot exhaust max_connections.
export DATABASE_POOL_SIZE="${DEPLOY_DATABASE_POOL_SIZE:-5}"