Drop python3.8 support core and providers#42742
Drop python3.8 support core and providers#42742jscheffl wants to merge 3 commits intoapache:mainfrom
Conversation
3aa9534 to
0578f53
Compare
|
Additionally ... This one should be done as a PR from So you will need to close that PR and re-open it by pushing your branch to the "apache" repository and open PR from there. When you will do it, the "pull_request_target" workflow will not be used at all - instead images will be built in the "Tests" workflow - and pushed to registry. This is because only PRS from the "main" repository can have write permissions (in this case "packages:write"). By default "pull_request" workflows have no "write" permissions and they would not be able to push the images to our registry - that's why for the "Fork" pull requests we need to build and push images in "pull_request_target" workflow - because it can have write permissions - but we have to make sure that this workflow uses only "approved" workflows and scripts from the "main" branch - rather than those that the PR is modifying. What happens in "pull_request_target" is that we check-out the PR from the fork, and before we run any scripts in our workflows, we override workflows, actions and scripts/ci folder with the version from |
Oh, wow. New learning. Did not know that with my committer power I actually could do... Continued in #42766 |
As Python 3.8 is getting out-of support, this PR removes support from Airflow providers and code.
See Python release schedule: https://peps.python.org/pep-0569/
Note: As I got a head-ache thinking about how to un-bundle the removal w/o 4-5PRs this is a combination with to commits from PR #42738 and #42739 - Maybe both is needed to make CI in Airflow v2-10 branch happy anyway.