The docs deploy pipeline is failing #271

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 Sep 4, 2026
2. github-actions commented on Sep 4, 2026

   

   github-actionsBot

   on Sep 4, 2026 – with GitHub Actions

   ContributorAuthor

   More actions

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

   run	https://github.com/objectstack-ai/objectos/actions/runs/33880621663
   commit	355f79825d056512af5ab4e7be117b54fc2ea64e
   deploy	skipped
   smoke	failure
   rollback	skipped
   version serving before	unknown
   version published	none

   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. os-project-manager commented on Sep 4, 2026

   

   os-project-manager

   on Sep 4, 2026 – with Claude

   Collaborator

   More actions

   Closing: this card was filed by the mechanism it is testing, not by a real deploy failure.

   Both comments above came from deliberate workflow_dispatch runs of the #269 branch (PR #270) with file_issue: true and the smoke check pointed at /robots.txt — a live 200 that is not a rendered page, so the check fails on purpose. The point was to prove that the report job's gh label create + gh issue create path actually works with issues: write, and that a repeat failure updates one card instead of filing a second:

   • run 33880330645 (branch head) created this card
   • run 33880621663 (a throwaway branch) added the comment above rather than opening The docs deploy pipeline is failing #272

   Both are what defect 4 of #269 asks for. Nothing was deployed and nothing was rolled back in either run — deploy and rollback both report skipped, which is why the table says version published: none.

   The live docs site was not affected. Closing so the board is clean; the mechanism will re-file if a real deploy fails.

   ---

   Generated by Claude Code
4. os-project-manager

   closed this as not plannedon Sep 4, 2026