ci: move the production docs deploy to Blacksmith and its build cache

Merged
SA
1mo ago
+21-6

Why

#8101 missed the production docs deploy. It stayed on a GitHub runner with no Next build cache, and the preview docs job lost its cache step because I wrongly believed production had no docs deploy.

What changes

  • Deploy Docs to Vercel runs on Blacksmith 4 vCPU and writes the Next build cache, like the other four apps.
  • The preview docs job restores that cache.
  • The five production deploy jobs install the Vercel CLI with bun, as the previews already do.

Verified

  • This PR's preview run is the first one after production wrote the Next build cache on main, so it also measures the warm path for API, Web, Marketing and Admin.

Not verified

  • The production side only runs on push to main.

Summary by cubic

Finishes the production deploy move that #8101 started, which missed the docs job. Docs now deploys on Blacksmith and writes a Next build cache that the preview job restores, and all five production deploy jobs install the Vercel CLI with bun instead of npm.

The production side only runs on push to main, so the warm cache path is only verified by the next production run.

Summary by CodeRabbit

  • Chores
    • Updated deployment workflows to reuse documentation build cache and install the deployment tool consistently. These changes affect deployment processes only; no user-facing functionality changed.