-
Notifications
You must be signed in to change notification settings - Fork 14.1k
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apache Airflow "latest" image is still Python 3.8 in Airflow 2.8.0 #36740
Comments
Looks strange.. It looks like the code is there and fixed .... puzzled a bit... But I will find out. |
Good catch! but yeah, it's very strange. Based in the CI log, it should be ok:
I checked the sha256 of the images we released one month ago to ensure that it is not a new issue, but it looks like we had the same issue with the RC images. |
Ah... I know .. my mistake. If you look here - it only changese at which python version the "2.8.0" alias points to latest one. There is no
But what should be changed is the line before that:
(and similar one in slim image) - > because THERE the "airflow:2.8.0-python3.8" gets the I will announce it at devlist that we are delaying it and remove the log in dockerfile changelog. |
In apache#36003 we **thought** we changed default "version" image to point to "newest" python version not to the "oldest" supported one - as agreed in https://lists.apache.org/thread/0oxnvct24xlqsj76z42w2ttw2d043oy3 However as observed and tracked in apache#36740 the change was not effective. We only changed the moment at which latest image is pointing to 2.8.0 but not whether 2.8.0 points to `python-3.8` or `python-3.11'. This means that we should only do that change for Python 3.9 qnd revert the changelog (and cherry-pick it to 2.8.1)
The change apache#36003 attempted to change which Python version is used for the "default" image ("2.8.0" and effectively "latest as well). But it failed to do so - because of a bug. The changelog about this have been removed in apache#36777 and we are bringing the change back (this time properly implemented) and changelog - with aim to release it in Airflow 2.9.0. Fixes: apache#36740
The change apache#36003 attempted to change which Python version is used for the "default" image ("2.8.0" and effectively "latest as well). But it failed to do so - because of a bug. The changelog about this have been removed in apache#36777 and we are bringing the change back (this time properly implemented) and changelog - with aim to release it in Airflow 2.9.0. Fixes: apache#36740
) In #36003 we **thought** we changed default "version" image to point to "newest" python version not to the "oldest" supported one - as agreed in https://lists.apache.org/thread/0oxnvct24xlqsj76z42w2ttw2d043oy3 However as observed and tracked in #36740 the change was not effective. We only changed the moment at which latest image is pointing to 2.8.0 but not whether 2.8.0 points to `python-3.8` or `python-3.11'. This means that we should only do that change for Python 3.9 qnd revert the changelog (and cherry-pick it to 2.8.1)
) In #36003 we **thought** we changed default "version" image to point to "newest" python version not to the "oldest" supported one - as agreed in https://lists.apache.org/thread/0oxnvct24xlqsj76z42w2ttw2d043oy3 However as observed and tracked in #36740 the change was not effective. We only changed the moment at which latest image is pointing to 2.8.0 but not whether 2.8.0 points to `python-3.8` or `python-3.11'. This means that we should only do that change for Python 3.9 qnd revert the changelog (and cherry-pick it to 2.8.1) (cherry picked from commit 270b112)
The change #36003 attempted to change which Python version is used for the "default" image ("2.8.0" and effectively "latest as well). But it failed to do so - because of a bug. The changelog about this have been removed in #36777 and we are bringing the change back (this time properly implemented) and changelog - with aim to release it in Airflow 2.9.0. Fixes: #36740
) In #36003 we **thought** we changed default "version" image to point to "newest" python version not to the "oldest" supported one - as agreed in https://lists.apache.org/thread/0oxnvct24xlqsj76z42w2ttw2d043oy3 However as observed and tracked in #36740 the change was not effective. We only changed the moment at which latest image is pointing to 2.8.0 but not whether 2.8.0 points to `python-3.8` or `python-3.11'. This means that we should only do that change for Python 3.9 qnd revert the changelog (and cherry-pick it to 2.8.1) (cherry picked from commit 270b112)
…che#36777) In apache#36003 we **thought** we changed default "version" image to point to "newest" python version not to the "oldest" supported one - as agreed in https://lists.apache.org/thread/0oxnvct24xlqsj76z42w2ttw2d043oy3 However as observed and tracked in apache#36740 the change was not effective. We only changed the moment at which latest image is pointing to 2.8.0 but not whether 2.8.0 points to `python-3.8` or `python-3.11'. This means that we should only do that change for Python 3.9 qnd revert the changelog (and cherry-pick it to 2.8.1)
…#36779) The change apache#36003 attempted to change which Python version is used for the "default" image ("2.8.0" and effectively "latest as well). But it failed to do so - because of a bug. The changelog about this have been removed in apache#36777 and we are bringing the change back (this time properly implemented) and changelog - with aim to release it in Airflow 2.9.0. Fixes: apache#36740
Body
Despite what is documented in Changelog and what we agreed in the lazy consensus , the default docker imagest (latest/latest-slim) are still pointing to Python 3.8.
The changelog should be corrected and that move should happen in Airflow 2.9
Committer
The text was updated successfully, but these errors were encountered: