zach-overflow opened a new pull request, #72977:
URL: https://github.com/apache/airflow/pull/72977
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
## What?
* Modifies `apache-airflow-task-sdk`'s dependency on `httpx` →
`httpx2`. The Execution API `Client` is now an `httpx2.Client`.
* Adds `certifi` as an explicit `task-sdk` dependency — `client.py` imports
it directly and it used to arrive via `httpx`, but `httpx2` depends on
`truststore` instead. TLS behaviour is unchanged: the client always passes its
own `ssl.SSLContext`.
* Moves `InProcessExecutionAPI.transport` / `.atransport` in `airflow-core`
to `httpx2`, plus the call sites that build or drive them. Objects don't cross
the `httpx`/`httpx2` boundary, and the only consumers of those transports are
Task SDK clients. The rest of `airflow-core` stays on `httpx`.
* Teaches `shared/logging` to suppress and mute both stacks, since
`airflow-core` and the Task SDK are now on different ones.
* Adds an [`ast-grep`](https://github.com/ast-grep/ast-grep) pre-commit
check to prevent re-introducing `httpx` in the Task SDK, mirroring the
providers one.
## Why?
* related: #70522
* follows: #72111
---
##### Was generative AI tooling used to co-author this PR?
- [x] Yes (please specify the tool below)
* 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)
* Scope of AI use:
* I pointed Claude Code at the `task-sdk` `httpx` usage and it did the
import replacements and dependency updates.
* It traced the cross-package boundary (in-process Execution API
transports, `devel-common` test helpers, prek scripts) and migrated those call
sites.
* It wrote the `ast-grep` rule and verified it fires.
* I reviewed the diff and wrote the PR description.
--
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]
