[zackpollard]

The docs-futo-cloud-prod production branch is prod, so main uploads only reached the main.* preview alias and docs.futo.cloud kept serving the old yucca build.

• main
  • fix(docs): deploy production to the prod pages branch #21 👈

[futo-kritika]

Kritika Review

Targets the prod Pages branch for production documentation deployments.

No findings

Confidence 4/5 · medium risk: The claim that the Pages project's production branch is prod rests only on the description. The review read nothing outside the repository and the account shows no check of it, so a mismatch would again leave docs.futo.cloud serving the old build. The rating is medium because the one-line deploy-script change is easy to revert and affects only the docs site.

Approved

Summary

The change aligns the production upload branch with the Pages configuration described in the pull request. It preserves the workflow's main-branch trigger and leaves pull-request preview routing unchanged.

Merge impact

• .github/workflows/docs.yml selects production on pushes to main, and packages/docs/.mise/tasks/deploy now submits those builds to docs-futo-cloud-prod with --branch=prod. Confirm the Pages project's production branch is prod and the resulting production deployment serves docs.futo.cloud; that project configuration lives outside this repository.

Review context · 0/6 commands

• Commands run: none

_{Reviews (1) · Last reviewed commit: "fix(docs): deploy production to the prod..." · openai/gpt-6.1-sol · $0.02}

[futo-kritika]

kritika: confidence 4/5 with medium risk at aafb56c.

[github-actions]

Docs preview (aafb56cbb5090d00f0d12f40aeaa0975c9dc957e)

https://pr-21.docs-futo-cloud-dev.pages.dev