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

   ### Body
   
   I have a kind request for all the contributors to the latest provider 
distributions 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_PROVIDERS.md#verify-the-release-candidate-by-contributors)
   
   Let us know in the comments, whether the issue is addressed.
   
   These are providers that require testing as there were some substantial 
changes introduced:
   
   
   ## Provider [fab: 
2.2.0rc1](https://pypi.org/project/apache-airflow-providers-fab/2.2.0rc1)
      - [ ] [Add `airflow db-manager` CLI for managing external databases 
(#50657)](https://github.com/apache/airflow/pull/50657): @ephraimbuddy
      - [ ] [Add support for unknown OIDC providers 
(#50921)](https://github.com/apache/airflow/pull/50921): @KKIEEK
      - [ ] [Move enable_swagger_ui config to api 
(#50896)](https://github.com/apache/airflow/pull/50896): @pierrejeambrun
      - [ ] [Move secret_key config to api section 
(#50839)](https://github.com/apache/airflow/pull/50839): @pierrejeambrun
      - [ ] [Move webserver config to fab provider 
(#50774)](https://github.com/apache/airflow/pull/50774): @pierrejeambrun
      - [ ] [Move webserver config options to api 
(#50693)](https://github.com/apache/airflow/pull/50693): @pierrejeambrun
      - [ ] [Remove unused entries from `DagAccessEntity` 
(#51174)](https://github.com/apache/airflow/pull/51174): @vincbeck
      - [ ] [Change v1 to v2 in generated OpenAPI schema files 
(#50705)](https://github.com/apache/airflow/pull/50705): @kaxil
   
   
   ### 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