potiuk commented on issue #52158: URL: https://github.com/apache/airflow/issues/52158#issuecomment-3001977836
Yes. As you might have read in the users@announcement this morning we regenerated the image. If you are not subscribed to the users@ devlist, please do - because otherwise you might miss important announcements from us and you might come to completely wrong conclusions (as you did this time). The message was here: https://lists.apache.org/thread/s9rkblzsdx9r5tff6nd59vfvw5tdry11 Also documentation on our docker stack documents the change here - you might want to go into details and see what has been changed: https://airflow.apache.org/docs/docker-stack/changelog.html#changes-after-publishing-the-images - see the first entry in the table. The changes were : new versions of `common.messaging` and `fab` providers (not `airflow`) which contain important bug-fixes were included in the image, also the image now contains `git` installed. None of those changes change versions nor code of `airflow-core` package - this is still version 3.0.2 exactly the same as it was when the code for 3.0.2 was frozen. So you are quite mistaken. Airlfow 3.0.2 is still there same as it was before. The image contains new version of providers - not airflow and add git. Very cccasionally (look at the doc of ours) we are pushing new image with those changes, meticulously document them and inform our users. If you find that some changes were implemented to "airflow-core 3.0.2" package - I would love to know, but there are none as far as I am concerned, becaus PROD. image installs packages from PyPI and it clearly shows `airflow" ``` ⏚ [jarek:~/IdeaProjects/airflow] move-ignores+ ± docker run -it apache/airflow:3.0.2-python3.11 bash -c 'pip freeze | grep airflow' apache-airflow==3.0.2 apache-airflow-core==3.0.2 apache-airflow-providers-amazon==9.8.0 apache-airflow-providers-celery==3.11.0 apache-airflow-providers-cncf-kubernetes==10.5.0 apache-airflow-providers-common-compat==1.7.0 apache-airflow-providers-common-io==1.6.0 apache-airflow-providers-common-messaging==1.0.3 apache-airflow-providers-common-sql==1.27.1 apache-airflow-providers-docker==4.4.0 apache-airflow-providers-elasticsearch==6.3.0 apache-airflow-providers-fab==2.2.1 apache-airflow-providers-ftp==3.13.0 apache-airflow-providers-git==0.0.2 apache-airflow-providers-google==15.1.0 apache-airflow-providers-grpc==3.8.0 apache-airflow-providers-hashicorp==4.2.0 apache-airflow-providers-http==5.3.0 apache-airflow-providers-microsoft-azure==12.4.0 apache-airflow-providers-mysql==6.3.0 apache-airflow-providers-odbc==4.10.0 apache-airflow-providers-openlineage==2.3.0 apache-airflow-providers-postgres==6.2.0 apache-airflow-providers-redis==4.1.0 apache-airflow-providers-sendgrid==4.1.0 apache-airflow-providers-sftp==5.3.0 apache-airflow-providers-slack==9.1.0 apache-airflow-providers-smtp==2.1.0 apache-airflow-providers-snowflake==6.3.1 apache-airflow-providers-ssh==4.1.0 apache-airflow-providers-standard==1.2.0 apache-airflow-task-sdk==1.0.2 google-cloud-orchestration-airflow==1.17.5 ``` And you are quite wrong about the messages. You might see yourself by changing the version to 3.0.1 and 3.0.0 and see that the messages were there from the very beginning of 3 line, so it's impossible they were added after 3.0.2 since they were there before. Please try not to jump to wrong conclusions before you make a bit more thorough check in the future. Closing as invalid. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
