The docs deploy pipeline is failing #391

Activity

1. github-actions

   added

   deploy-failureAutomated: the docs deploy or its post-deploy smoke check failedAutomated: the docs deploy or its post-deploy smoke check failed

   on Oct 29, 2026
2. github-actions commented on Oct 29, 2026

   

   github-actionsBot

   on Oct 29, 2026 – with GitHub Actions

   ContributorAuthor

   More actions

   Automated report from ci.yml -> deploy-docs.yml.

   run	https://github.com/objectstack-ai/docs.objectos.ai/actions/runs/40862958838
   commit	3bbc710dcb811cb93013f5470f5d700e7a42eb86
   deploy	success
   smoke	failure
   rollback	success
   version serving before	2daf9109-12f8-4507-90b0-d0a3d0e187ee
   version published	b997c02e-9157-4719-b1f0-030939004602

   A deploy failure with no published version usually means Cloudflare
   refused the upload — while #261 is open that is the expected steady
   state and the live site is unaffected. A smoke failure means the
   live site did not render; the run log names which rule fired.
3. objectstack-fleet commented on Oct 29, 2026

   

   objectstack-fleetBot

   on Oct 29, 2026

   Contributor

   More actions

   Seat note · 2026-10-29T11:32Z · session_01QsR2jTaZ2GeyfjANMwstiw · seat repo:docs.objectos.ai#1

   main deploys again. #392 reverted #390 and merged as 09784e7. Main CI run 40865527189 is green: Publish success, the new version is serving, and the smoke check passed, with search answering in all eight locales.

   The cause was memory, not a flake. /api/search keeps every locale's Orama index in one isolate, 30–40 MB each, and #390's ja pages pushed it over the Worker limit. The heap measurement and the fix are tracked on #393, and #390's pages re-land after that fix. Closing this failure card.
4. objectstack-fleet

   closed this as completedon Oct 29, 2026