potiuk opened a new pull request #14227:
URL: https://github.com/apache/airflow/pull/14227


   There are two types of constraints now:
   
   * default constraints that contain all depenedncies of airflow,
     all the provider packages released at the time of the relese
     of that version, as well as all transitive dependencies. Following
     those constraints, you can be sure Airflow's installation is
     repeatable
   
   * no-provider constraints - containing only the dependencies needed
     for core airflow installation. This allows to install/upgrade
     airflow without also forcing the provider's to be installed at
     specific version of Airflow.
   
   This allows for flexible management of Airflow and Provider
   packages separately. Documentation about it has been added.
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   


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

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to