Skip to content

Update provider READMEs for the Python 3.11 baseline - #74158

Open
shahar1 wants to merge 1 commit into
drop-py310/7-pyproject-metadatafrom
drop-py310/8-provider-readmes
Open

shahar1 wants to merge 1 commit into
drop-py310/7-pyproject-metadatafrom
drop-py310/8-provider-readmes

Conversation

@shahar1

@shahar1 shahar1 commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

As titled - this PR updates provider READMEs for the Python 3.11 baseline.

related: #74148

AI Summary The "supports the following python versions" line in each provider `README.rst` drops 3.10. These files are regenerated at provider release time; keeping the committed copies in step with `pyproject.toml` avoids a misleading diff in the next provider wave. One-line change per file.

Stack

Layer 8 of 9 of the Python 3.10 drop (supersedes #74144, which carried the whole change in one PR). Each layer is meant to be green on its own: the script metadata bump comes first because prek picks the hook interpreter from it, and the ruff fixes land before the requires-python bump because ruff infers its target per distribution from the nearest pyproject.toml.

  1. Drop Python 3.10 from CI, Breeze and the container images
  2. Bump inline script metadata to Python 3.11
  3. Remove Python 3.10 compatibility shims
  4. Apply ruff Python 3.11 fixes to core, Task SDK, shared and airflowctl
  5. Apply ruff Python 3.11 fixes to providers
  6. Apply ruff Python 3.11 fixes to dev tooling, scripts and test suites
  7. Require Python 3.11 in all distributions
  8. Update provider READMEs for the Python 3.11 baseline
  9. Update docs for the Python 3.11 baseline

Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Fable 5.1)

Generated-by: Claude Code (Fable 5.1) following the guidelines

@shahar1
shahar1 force-pushed the drop-py310/8-provider-readmes branch from adc8206 to 82d232c Compare October 3, 2026 13:07
@shahar1
shahar1 added this pull request to stack #74160 October 3, 2026 13:08
@shahar1 shahar1 added the skip common compat check Skips common compat provider modification check label Oct 3, 2026
@shahar1 shahar1 mentioned this pull request Oct 3, 2026
1 task done
@shahar1
shahar1 force-pushed the drop-py310/8-provider-readmes branch from 82d232c to 2c9b8e1 Compare October 3, 2026 13:38
@shahar1
shahar1 marked this pull request as ready for review October 3, 2026 13:59
@shahar1
shahar1 force-pushed the drop-py310/8-provider-readmes branch from 2c9b8e1 to ddee4bc Compare October 3, 2026 15:00
@shahar1
shahar1 force-pushed the drop-py310/8-provider-readmes branch from ddee4bc to 41efa66 Compare October 3, 2026 20:05
@shahar1
shahar1 force-pushed the drop-py310/8-provider-readmes branch from 41efa66 to 8d4ed84 Compare October 4, 2026 17:53
@shahar1 shahar1 added the ready for maintainer review Set after triaging when all criteria pass. label Oct 4, 2026
@shahar1
shahar1 force-pushed the drop-py310/8-provider-readmes branch from 8d4ed84 to ccee579 Compare October 4, 2026 18:57
The supported Python version list in each provider README is
regenerated at release time, but keeping the committed copies in step
with the pyproject.toml metadata avoids a misleading diff in the next
provider wave.
@potiuk
potiuk force-pushed the drop-py310/8-provider-readmes branch from ccee579 to e00f6ae Compare October 4, 2026 23:43

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready for maintainer review Set after triaging when all criteria pass. skip common compat check Skips common compat provider modification check

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant