The GitHub Actions job "Tests" on airflow.git/v3-2-test has succeeded. Run started by GitHub user eladkal (triggered by eladkal).
Head commit for run: afd9a20919d2fe408b22cc4d21353c45ba5c6971 / github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> [v3-2-test] docs(security): clarify Task Execution API coverage in DAG-author-isolation chapter (#66194) (#66322) Add an explicit paragraph to the "Limiting Dag Author access to subset of Dags" chapter making clear it covers the Task Execution API used by the Task SDK, not only the UI / public REST API. The existing chapter already states that "regardless of execution context, Dag authors have access to all Dags" and that "workloads from different teams still share the same Execution API". Readers nonetheless ask whether the Execution JWT enforces per-Dag authorization. The new paragraph answers that explicitly: it does not, and `ti:self` is not a per-Dag access control. (cherry picked from commit 2d200ecfb75a05a2f1529bc048f182a3cce06d1e) Generated-by: Claude Opus 4.7 (1M context) following the guidelines at https: //github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions Co-authored-by: Jarek Potiuk <[email protected]> Report URL: https://github.com/apache/airflow/actions/runs/25379439381 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
