Skip to content

Status of testing Providers that were prepared on January 13th, 2026 #60496

Closed

Description

@jscheffl

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-contributo

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 airbyte: 5.3.2rc1

Provider alibaba: 3.3.3rc1

Provider amazon: 9.20.0rc1

Provider apache.beam: 6.2.2rc1

Provider apache.hdfs: 4.11.2rc1

Provider apache.hive: 9.2.3rc1

Provider apache.impala: 1.8.1rc1

Provider apache.livy: 4.5.2rc1

Provider apache.spark: 5.5.0rc1

Provider celery: 3.15.1rc1

Provider cncf.kubernetes: 10.12.1rc1

Provider common.compat: 1.12.0rc1

Provider common.io: 1.7.1rc1

Provider common.sql: 1.30.3rc1

Provider databricks: 7.8.3rc1

Provider dbt.cloud: 4.6.3rc1

Provider discord: 3.12.0rc1

Provider docker: 4.5.2rc1

Provider edge3: 3.0.0rc1

Provider exasol: 4.9.1rc1

Provider fab: 3.1.2rc1

Provider google: 19.4.0rc1

Provider hashicorp: 4.4.2rc1

Provider http: 5.6.3rc1

Provider imap: 3.10.3rc1

Provider keycloak: 0.5.0rc1

Provider microsoft.azure: 12.10.2rc1

Provider microsoft.winrm: 3.13.3rc1

Provider odbc: 4.11.1rc1

Provider openai: 1.7.2rc1

Provider openlineage: 2.10.0rc1

Provider postgres: 6.5.2rc1

Provider presto: 5.10.3rc1

Provider redis: 4.4.2rc1

Provider sftp: 5.6.0rc1

Provider snowflake: 6.8.2rc1

Provider ssh: 4.3.0rc1

Provider standard: 1.10.3rc1

Provider teradata: 3.4.1rc1

Provider trino: 6.4.2rc1

Provider vertica: 4.2.1rc1

Provider yandex: 4.3.2rc1

All users involved in the PRs:
@bgshacklett @jscheffl @chirodip98 @amoghrajesh @shahar1 @trina242 @AutomationDev85 @Srabasti @junaiddshaukat @arjav1528 @Dev-iL @SameerMesiah97 @justinp

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Activity

  1. added
    kind:metaHigh-level information important to the community
    on Jan 14, 2026
  2. marcosmartinezfco commented on Jan 14, 2026

    @marcosmartinezfco

    Just my two cents here, I've tested amazon: 9.20.0rc1 in my set up and works just fine. It fixes my original issue #60223.

    Will leave it up to @justinpakzad to give the official approval though. Many thanks

  3. chirodip98 commented on Jan 14, 2026

    @chirodip98
    Contributor

    I tested for the DataprocDeleteCluster Operator (google-provider) , works fine on my System (locally).
    Let me know if any further testing , evidences are required

  4. dondaum commented on Jan 14, 2026

    @dondaum
    Contributor

    I have successfully tested all my changes with Airflow==3.1.6:

    #58603 ✅

    I installed the pre-release provider packages and ran a test DAG.

  5. junaiddshaukat commented on Jan 14, 2026

    @junaiddshaukat
    Contributor

    I have verified apache-airflow-providers-fab==3.1.2rc1.

  6. henry3260 commented on Jan 14, 2026

    @henry3260
    Contributor

    That works great with all my changes. :)

  7. raphaelauv commented on Jan 14, 2026

    @raphaelauv
    Contributor

    tested my changes ( #60041 )

    works well ✔️

    apache-airflow-providers-apache-spark==5.5.0rc1
    pyspark-client==4.1.1

    def test(spark):
        df = spark.range(100).filter("id % 2 = 0")
        print(df.count())
    
    PySparkOperator(task_id="task",
                    python_callable=test,
                    conn_id="spark_connect")
  8. anishgirianish commented on Jan 14, 2026

    @anishgirianish
    Contributor

    My changes looks all set #60109 ✅

  9. potiuk commented on Jan 14, 2026

    @potiuk
    Member

    Checked all dependency changes where I was involved -> looks good !

  10. ecodina commented on Jan 14, 2026

    @ecodina
    Contributor

    Checked my change for keycloak (#59411) and it works well.

  11. quentin-sommer commented on Jan 14, 2026

    @quentin-sommer
    Contributor

    Ok for
    #60231

  12. stephen-bracken commented on Jan 14, 2026

    @stephen-bracken
    Contributor

    Confirmed #53368 and #60372 are working as expected
    using apache-airflow==3.1.6 and apache-airflow-providers-cncf-kubernetes==10.12.1rc1
    with airflow standalone on kubernetes v1.33.5

  13. justinpakzad commented on Jan 14, 2026

    @justinpakzad
    Contributor

    Checked all my changes - all good.

  14. SameerMesiah97 commented on Jan 15, 2026

    @SameerMesiah97
    Contributor

    I can verify that the changes introduced in PR #60027 are working as expected in apache-airflow-providers-snowflake==6.8.2rc1

  15. steveahnahn commented on Jan 15, 2026

    @steveahnahn
    Contributor

    Looks good on #60244 & #59944

  16. dheerajturaga commented on Jan 15, 2026

    @dheerajturaga
    Member

    @jscheffl, I was able to scale test apache-airflow-providers-edge3 3.0.0rc1 my findings posted on #56457

    everything is working as expected, thanks for the major update!

  17. sunank200 commented on Jan 15, 2026

    @sunank200
    Collaborator

    I tested my changes for 59991, 59993, 59979, 59966, 59989, 59988, 59986, 59994, 59995, 59996, 60026, 59921, 59984, 59983, 59970, 59981, 59968 and 59992. Everything is working as expected.

  18. amoghrajesh commented on Jan 15, 2026

    @amoghrajesh
    Contributor

    Majority of my changes this time are around doing some big changes in core and sdk.

    Plugins manager: #59956, Listeners Manager: #59883 and those providers install fine.

    Other functional changes: #60324 for cncf, compat sdk for AirflowConfigException: #60044 and #60042 for CI work fine.

  19. jason810496 commented on Jan 15, 2026

    @jason810496
    Member

    Thanks Jens! I just checked all the providers related to my change (#59805). Even though it will only affect after 3.2.x , and will not affect on any 3.1.x.

  20. KamranImaaz commented on Jan 15, 2026

    @KamranImaaz
    Contributor

    Hi @jscheffl I tested the change from #59866 using apache-airflow-providers-google==19.4.0rc1. And It Looks Good from my side.

  21. ricky-chaoju commented on Jan 16, 2026

    @ricky-chaoju
    Contributor

    I tested the change from #60322 using apache-airflow-providers-google==19.4.0rc1. Looks good from my side.

  22. jscheffl commented on Jan 17, 2026

    @jscheffl
    ContributorAuthor

    Thank you everyone. Providers are released.

    Wow, impressive responses for all release checks! Thanks!

    I invite everyone to help improve providers for the next release, a list of open issues can be found here.

  23. berglh commented on Jan 17, 2026

    @berglh

    The failure mode for apache-airflow-providers-fab in #59349 is not easily reproducible as it occurs some time after restarting the API server. Nevertheless, initial reports seem to be positive from those of us that have been testing apache-airflow-providers-fab==3.1.2rc1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:providerskind:metaHigh-level information important to the community

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions