soooojinlee opened a new pull request, #60999:
URL: https://github.com/apache/airflow/pull/60999

   Switch DAG templating to a zip-aware loader that preserves searchpath order 
and applies the same path traversal rules as FileSystemLoader. Add tests for 
mixed paths, ordering, and zip traversal blocking.
   
   ## Summary
   - Add a zip-aware Jinja2 loader to resolve templates from zipped DAGs.
   - Preserve searchpath ordering and apply FileSystemLoader-equivalent path 
validation to zip paths.
   - Consolidate zipped DAG template tests into task-sdk DAG tests (mixed 
paths, ordering, traversal blocking).
   
   ## Test plan
   - uv run pytest task-sdk/tests/task_sdk/definitions/test_dag.py -v --tb=short
   - prek --all-files (local failures: Docker not running for OpenAPI spec 
hooks; FAB assets yarn install failed with 502)
   
   ## Docs
   - N/A
   
   ## Breaking changes
   - N/A
   
   ## Related
   - Fixes [#59310](https://github.com/apache/airflow/issues/59310)
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   - [x] Yes (please specify the tool below)
   Generated-by: Claude Opus 4.5
   
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
   


-- 
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]

Reply via email to