vatsrahul1001 opened a new pull request, #71152: URL: https://github.com/apache/airflow/pull/71152
The `Release constraints` workflow (added in #71040) gates its `build-info` job on an actor allowlist. It seeded that list with the standard committer set but omitted `vatsrahul1001`, who is already on the allowlist of the sibling release workflows (`publish-docs-to-s3.yml`, `release_dockerhub_image.yml`, `update-constraints-on-push.yml`). As the **3.3.1 release manager**, he needs to dispatch this workflow to generate the RC/final constraints (the new `start-rc-process` / `start-release` flow triggers it). Without the entry, a `workflow_dispatch` by him **skips the entire run** (the `build-info` gate evaluates false), e.g. run 30980170144. This adds him, filling the gap rather than granting new access. `backport-to-v3-3-test` set so it applies on the 3.3.1 release branch too. ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 4.8) Generated-by: Claude Code (Opus 4.8) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) — one-line allowlist addition. -- 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]
