potiuk opened a new pull request, #76168: URL: https://github.com/apache/airflow/pull/76168
Publishing docs and the provider registry builds a full CI image on public runners, which are slower and queue behind the rest of the project's jobs. `publish-docs-to-s3.yml`, `registry-build.yml` and `registry-backfill.yml` now pick their runners the same way CI does: a small `ubuntu-slim` job runs `breeze ci selective-check` from the workflow's own version and every other job runs on the RunsOn label it returns, sized per job. The `USE_PUBLIC_RUNNERS` repository variable still moves them back to public runners. The registry build checks out the ref being published, and older refs ship a `make_mnt_writeable.sh` that empties `/mnt` — on RunsOn that holds the runner's own disks — so it now runs the runner-preparation scripts from the workflow's version, as the docs build already did. The selective-check job only gets `run_id` and `ref_name` rather than the whole GitHub context, since it runs before the committer allowlist and the full context would carry the dispatch inputs. --- ##### 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) 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
