o-nikolas opened a new pull request, #72169: URL: https://github.com/apache/airflow/pull/72169
Two steps of the provider release depend on access that someone else has to grant, and both fail in ways that are hard to interpret in the middle of a wave: * **PyPI membership of the `apache-airflow` organization** — without it you cannot create a token that can publish the `apache-airflow-providers-*` projects, and you find out only at the upload step, after the artifacts are built, signed and already committed to SVN. * **The docs-publishing allowlist in `publish-docs-to-s3.yml`** — the workflow gates `build-info` on `github.event.sender.login` and every other job depends on it, so a dispatch by someone not on the list reports **no error**: the run is created and all jobs are silently skipped. This is the same trap already fixed for individuals in #71848 / #72080, but nothing in the release docs tells a new release manager to get themselves added, or that the list is read from the workflow file at the dispatched ref (so the PR must be merged to `main` first). Both are one-time per person and neither is instant, so this adds a short section at the start of the RC process telling release managers to request them up front, with the symptom of each failure and a way to verify the access is in place. The existing GPG/`KEYS` readiness check is cross-referenced rather than duplicated. Found while running the 2026-08-25 provider wave, where both blocked the release mid-flight. **Tested:** docs-only change; the doctoc hook regenerated the table of contents and `prek run --from-ref upstream/main --stage pre-commit` is clean. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Kiro CLI (claude-fable-5) Generated-by: Kiro CLI (claude-fable-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]
