Revert the pandas < 3 cap for DataFrame XComs (backport of #71100) - #71182
Merged
Conversation
Backport of #71100, which reverted "Limit pandas to < 3 for DataFrame XComs" (#70791) on main. v3-3-test carried the cap via the #70912 backport; reverting that commit removes the cap here too so the release branch matches main. The pandas-3 XCom serializer support lands separately in #71169 (the #71103 backport) -- the same order main used (#71100 before #71103). uv.lock regenerated with uv 0.12.1 to drop the pandas <3 specifier.
vatsrahul1001
requested review from
amoghrajesh,
ashb,
kaxil,
o-nikolas,
potiuk and
shahar1
as code owners
August 5, 2026 14:06
boring-cyborg
Bot
added
area:providers
area:task-sdk
kind:documentation
provider:amazon
amoghrajesh
approved these changes
Aug 5, 2026
vatsrahul1001
added a commit
that referenced
this pull request
Aug 5, 2026
Backport of #71100, which reverted "Limit pandas to < 3 for DataFrame XComs" (#70791) on main. v3-3-test carried the cap via the #70912 backport; reverting that commit removes the cap here too so the release branch matches main. The pandas-3 XCom serializer support lands separately in #71169 (the #71103 backport) -- the same order main used (#71100 before #71103). uv.lock regenerated with uv 0.12.1 to drop the pandas <3 specifier.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #71100 to
v3-3-test— the pandas<3cap for DataFrame XComs was reverted onmainand needs the same on the release branch.Why this reverts #70912 rather than cherry-picking #71100
The cap reached
v3-3-testthrough the backport #70912 (of #70791). Cherry-picking main's revert (#71100) conflicts heavily because the provider docs/README/pyproject have diverged (main's provider versions are newer). Revertingv3-3-test's own cap commit (#70912) is the equivalent, clean way to remove it — all 40 provider files, the task-sdk serializer, and the newsfragment revert cleanly.uv.lockwas regenerated (with uv 0.12.1, satisfying the repo'suv>=0.11.21) — the diff is exclusively the pandas<3specifier being dropped across the provider extras, no unrelated bumps.Sequencing
The pandas-3 XCom serializer support lands separately in #71169 (the #71103 backport). This matches main's order — #71100 (revert cap) before #71103 (add support). Once this merges, #71169 may need a quick rebase since both touch
task-sdk/.../serializers/pandas.py.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines