potiuk commented on issue #36384:
URL: https://github.com/apache/airflow/issues/36384#issuecomment-1874050313

   > 
https://raw.githubusercontent.com/apache/airflow/constraints-2.8.0/constraints-3.11.txt
 or any python versions will be updated to take into account the latest 
providers versions ? The next apache-airflow release (2.8.1) ?
   
   Released constraints are almost never updated (the only case they are 
updated is when for some reason airflow is not installable with them). This is 
explained here 
https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html#constraints-files
  : constraints are there to provide reproducible installation of Airflow - 
with THE SAME packages that it was released with originally.
   
   If you want to upgrade to latest providers, you should install them without 
constraints. This is explained  in 
https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html#installation-and-upgrade-scenarios
 and in this talk from Airflow Summit 2023: 
https://airflowsummit.org/sessions/2023/mastering-dependencies-the-airflow-way/ 
(I recommend reading it / watching the talk).
   
   The constraints are updated (when tests pass):
   
   * 
https://github.com/apache/airflow/blob/constraints-main/constraints-3.10.txt - 
for main version of Airflow
   * 
https://github.com/apache/airflow/blob/constraints-v2-8-test/constraints-3.10.txt
 - for latest branch (this is happenning when we start cherry-picking for new 
release - it's updated irregularly
   
   In case of 
https://github.com/apache/airflow/blob/constraints-v2-8-test/constraints-3.10.txt
  - when we release 2.8.1, those constraints will become 2.8.1 and (as well as 
2.8.0) will be frozen and will not be updated any more.
   


-- 
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

Reply via email to