You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/03/21 16:58:00 UTC

[GitHub] [airflow] potiuk edited a comment on issue #22264: Status of testing Providers that were prepared on March 15, 2022

potiuk edited a comment on issue #22264:
URL: https://github.com/apache/airflow/issues/22264#issuecomment-1074158789


   > dumb question: will these new providers show up in the [constraints-2.2.4/constraints-3.8.txt](https://raw.githubusercontent.com/apache/airflow/constraints-2.2.4/constraints-3.8.txt)? or be pushed to Airflow 2.2.5?
   
   The latter. 
   
   The constraints for each version contain the "snapshot" of providers that are available during release.
   
   Constraints for released version (so `constraints-2.2.4` for example) are very rarely updated unless we want to bugfix some dependency issue. 
   
   You are free to upgrade the new providers individually as described in https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html#installation-and-upgrading-of-airflow-providers-separately (just mind that this wave will be re-run as they have mistakenly two extra packages as dependencies so I think about yanking all of them after we release a new wave). But for the "base" installation of airflow using constraints, stability of the installation is more important than using newer providers.
   
   


-- 
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-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org