potiuk opened a new pull request, #70912:
URL: https://github.com/apache/airflow/pull/70912
Backport of #70791 to `v3-3-test`.
Under pandas 3 a DataFrame does not round trip through an XCom the way it
does under
pandas 2, so the pandas dependency is capped at `<3` everywhere Airflow
declares it,
backed by a runtime check in the Task SDK serializer.
### Conflict resolution
The cherry-pick conflicted in ten files. Every conflict came from unrelated
`main`-only
changes rather than from the pandas work itself, so in each case the
`v3-3-test` side was
kept and only the pandas cap was taken:
- `providers/exasol/pyproject.toml`, `providers/weaviate/pyproject.toml` —
kept the
branch pins (`pyexasol>=0.26.0`, `weaviate-client>=4.4.0`); the `main`
side also carried
a `pyexasol<2` cap and a `weaviate-client>=4.16.0` bump that belong to
other PRs.
- `providers/{amazon,common/sql,postgres}/docs/index.rst` — `main` adds an
"Optional
dependencies" section generated by tooling that does not exist on
`v3-3-test`, so these
three files end up unchanged here.
- exasol/weaviate `README.rst` and `docs/index.rst` — took the pandas rows
and table
widths, restored the branch's client pins.
- `uv.lock` — regenerated with the branch's pinned uv `0.11.21` rather than
hand-merged.
The lock diff is larger than the pandas rows alone because capping pandas
collapses a
dual-version resolution fork, which in turn simplifies markers on `caio`,
`aiohttp`,
`typing-extensions` and `adbc-driver-manager`. Regenerating the lock on an
otherwise
pristine `v3-3-test` tree with the same uv produces a zero diff, confirming
none of that
churn is uv-version drift.
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Opus 5 (1M context)
Generated-by: Claude Opus 5 (1M context) 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]
