potiuk opened a new pull request, #71305: URL: https://github.com/apache/airflow/pull/71305
`breeze workflow-run publish-docs` dispatches three workflows in sequence — `publish-docs-to-s3` on apache/airflow, then the apache/airflow-site refresh, then the apache/airflow-site-archive S3-to-GitHub sync — and gates each on the previous one finishing. Two things broke that gate. **It monitored whichever run was newest, not the one it dispatched.** `gh run list --limit 1` was called right after the dispatch. When the dispatch had not registered yet, that returns the *previous* run — typically already finished — so the driver declared success and moved straight on to the two follow-up workflows while the docs build it was supposed to wait for was still running. A scheduled run, or a run another maintainer started, was picked up the same way. Run ids increase monotonically, so the id observed just before dispatching is now recorded and the driver waits (up to 3 minutes) for a run above it. **Only `failure` was treated as a failure.** A run that came back `cancelled`, `timed_out`, or `action_required` fell through the terminal branch without exiting, and the rest of the chain proceeded as if the docs had been published. Any conclusion other than `success` now fails the command. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 5) Generated-by: Claude Code (Opus 5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
