eladkal opened a new issue, #34302:
URL: https://github.com/apache/airflow/issues/34302

   ### Body
   
   I have a kind request for all the contributors to the latest provider 
packages release.
   Could you please help us to test the RC versions of the providers?
   
   The guidelines on how to test providers can be found in
   
   [Verify providers by 
contributors](https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-contributors)
   
   Let us know in the comment, whether the issue is addressed.
   
   Those are providers that require testing as there were some substantial 
changes introduced:
   
   
   ## Provider [dbt.cloud: 
3.3.0rc2](https://pypi.org/project/apache-airflow-providers-dbt-cloud/3.3.0rc2)
      - [ ] [openlineage, dbt: add OpenLineage support for DBT Cloud 
(#33959)](https://github.com/apache/airflow/pull/33959): @JDarDagran
      - [ ] [respect soft_fail argument when exception is raised for dbt 
sensors (#34164)](https://github.com/apache/airflow/pull/34164): @Lee-W
      - [ ] [dbt, openlineage: set run_id after defer, do not log error if 
operator has no run_id set 
(#34270)](https://github.com/apache/airflow/pull/34270): @mobuchowski
      - [ ] [Remove some useless try/except from providers code 
(#33967)](https://github.com/apache/airflow/pull/33967): @hussein-awala
      - [ ] [Use a single  statement with multiple contexts instead of nested  
statements in providers 
(#33768)](https://github.com/apache/airflow/pull/33768): @hussein-awala
   
   <!--
   
      - [ ] [Prepare docs for 09 2023 - 1st wave of Providers 
(#34201)](https://github.com/apache/airflow/pull/34201): @eladkal
   
   -->
   
   All users involved in the PRs:
   @JDarDagran @mobuchowski @Lee-W @hussein-awala
   
   ### Committer
   
   - [X] I acknowledge that I am a maintainer/committer of the Apache Airflow 
project.


-- 
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: [email protected]

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

Reply via email to