potiuk commented on issue #48083: URL: https://github.com/apache/airflow/issues/48083#issuecomment-2749726582
Also Note that we have a solution described here: https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html which precisely describes how you can **reproducibly** install released version Airflow using constraint files generated and published by Airflow maintainers. This is the way how you can reproducibly (again) install airflow regardless if a new version (including broken version) of one of 700+ libraries of airflow has been released. Are you aware about this mechanism? Are you using it with Composer? Have you checked with Composer support if you can use it? Did you try it? I think it's a good idea to do a research and follow the advices (constraints I mantioned above) of maintainers, that actuallly **solved** the problem already 4 years ago actually providing a mechanims which protects our users from broken released of 3rd-parties. But, we can't do much if our users do not use those mechanisms we provided. So I'd stronly advise you to look what you can do to follow those advices. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
