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

   ### 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 comments, whether the issue is addressed.
   
   **NOTE Changes tested on 
[RC1](https://github.com/apache/airflow/issues/45957) were automatically marked 
as tested for RC2**
   
   
   These are providers that require testing as there were some substantial 
changes introduced:
   
   
   ## Provider [celery: 
3.10.0rc2](https://pypi.org/project/apache-airflow-providers-celery/3.10.0rc2)
      - [ ] [Add support for custom celery configs 
(#45038)](https://github.com/apache/airflow/pull/45038): @arorasachin9
      - [ ] [Fix Version Check for CLI Imports in Providers 
(#45255)](https://github.com/apache/airflow/pull/45255): @bugraoz93
      - [ ] [AIP-72: Support DAG parsing context in Task SDK 
(#45694)](https://github.com/apache/airflow/pull/45694): @kaxil
      - [ ] [AIP-72: Support better type-hinting for Context dict in SDK  
(#45583)](https://github.com/apache/airflow/pull/45583): @kaxil
   
   <!--
   
   NOTE TO RELEASE MANAGER:
   
   You can move here the providers that have doc-only changes or for which 
changes are trivial, and
   you could assess that they are OK.
   
   -->
   All users involved in the PRs:
   @arorasachin9 @kaxil @bugraoz93
   
   
   
   
   ### 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