Remove Python 3.7 support

[potiuk]

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[potiuk]

Marked as "Ready for review" - should be such and I guess we can merged it soon after @eladkal's lazy consensus.

The doubt was raised whether the providers should be 3.8+ only as well - I believe so, it's the same reason we speed up the removal in CI, so providers should be 3.8+ as well IMHO.

[eladkal]

The doubt was raised whether the providers should be 3.8 only as well - I believe so

They should be 3.8+

[potiuk]

So - it's all green, ready to final review and merge :)

[pankajkoti]

Just wish to check if we need to tag this to some milestone and if need to also apply the pinned label like in PR #27264?

[potiuk]

Just wish to check if we need to tag this to some milestone and if need to also apply the pinned label like in PR #27264?

No need. We are not cherry-picking it to 2.6 (so by default it goes to next major relase). And pinned was really there to make sure the 3.11 PR is not closed automatically by the stalebot (the 3.11 was opened in October and it has long period of waiting for dependencies to catch up, so I wanted to make sure stalebot will not close it. The "pinned" label is specifically for stalebot.

[raphaelauv]

README of branch main is no more showing 3.7 as a valide version for 2.6.1

Is that voluntary ?

[potiuk]

README of branch main is no more showing 3.7 as a valide version for 2.6.1

Is that voluntary ?

Nope. mistake.

[potiuk]

Fix in #31592

[pankajkoti]

Just wish to check if we need to tag this to some milestone and if need to also apply the pinned label like in PR #27264?

No need. We are not cherry-picking it to 2.6 (so by default it goes to next major relase). And pinned was really there to make sure the 3.11 PR is not closed automatically by the stalebot (the 3.11 was opened in October and it has long period of waiting for dependencies to catch up, so I wanted to make sure stalebot will not close it. The "pinned" label is specifically for stalebot.

Okay, understood, nice. Checked it here now that how we save such PRs from the Stalebot here: https://github.com/apache/airflow/blob/main/.github/workflows/stale.yml#L40