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


   This fixes #12255 - where we published beta2 release with some
   extras pulling non-existing providers.
   
   The exact list of providers that had problems:
   
   Wrongly named extras/providers:
   
   * apache.presto: it was badly named -> renamed to 'presto'
   * spark (badly pointing to spark instead of apache.spark)
   * yandexcloud (the name remains there but we've also added 'yandex' extra to 
correspond 1-1 with 'yandex' provider
   
   Extras that were wrongly marked as having providers, where they had
   none:
   
   * dask
   * rabbitmq
   * sentry
   * statsd
   * tableau
   * virtualenv
   
   <!--
   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