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


   With the upcoming apache-beam change where mock library will be
   removed from install dependencies, we will be able to remove
   `apache-beam` exclusion in our CI scripts. This will be a final
   step of cleaning dependencies so that we have a truly
   golden set of constraints that will allow to install airflow
   and all community managed providers (we managed to fix all those
   dependency issues for all packages but apache-beam).
   
   The fix https://github.com/apache/beam/pull/14328 when merged
   and Apache Beam is released will allow us to migrate to the new
   version and get rid of the CI exclusion for beam.
   
   Closes: #14994
   
   <!--
   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