Skip to content

Status of testing Providers that were prepared on June 19, 2026 #68751

Closed

Description

@shahar1

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

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 alibaba: 3.3.9rc1

Provider amazon: 9.31.0rc1

Provider apache.hdfs: 4.12.1rc1

Provider apache.spark: 6.2.0rc1

Provider clickhousedb: 1.0.0rc2 🎉 New provider

Note: This is a new provider, so the PRs below are collected from the git history of the provider's sources rather than from a changelog diff. The list may therefore include bootstrap and development commits (e.g. release-preparation commits) that are not user-facing changes.

Provider cncf.kubernetes: 10.18.1rc1

Provider common.ai: 0.5.0rc1

Provider databricks: 7.16.1rc1

Provider edge3: 4.0.0rc1

Provider elasticsearch: 6.7.0rc1

Provider fab: 3.7.0rc1

Provider ftp: 3.15.1rc1

Provider google: 22.2.0rc1

Provider hashicorp: 4.7.1rc1

Provider http: 6.0.4rc1

Provider keycloak: 0.8.0rc1

Provider microsoft.azure: 13.5.0rc1

Provider microsoft.mssql: 4.7.0rc1

Provider openlineage: 2.18.1rc1

Provider opensearch: 1.10.0rc1

Provider postgres: 6.8.0rc1

Provider redis: 4.5.0rc1

Provider sftp: 5.8.2rc1

Provider snowflake: 6.14.0rc1

Provider ssh: 5.0.3rc1

Provider standard: 1.15.0rc1

Provider weaviate: 3.3.5rc1

All users involved in the PRs:
@kaxil @jscheffl @Vrutik-0 @sejal-gupta-ksolves @gopidesupavan @nailo2c @FrankYang0529 @litesh1998 @dfgvaetyj3456356-hash @Vamsi-klu @shubhamraj-git @seungoh-lee @fpopic @jason810496 @orbisai0security @yuseok89 @jayachandrakasarla @VladaZakharova @amoghrajesh @ferruzzi @iwannagotobed @kacpermuda @dabla @henry3260 @shahar1 @Dotify71 @imrichardwu @johnhoran @pcorliss @AlejandroMorgante @vincbeck @23tae @potiuk @vchomakov @SameerMesiah97 @bugraoz93 @justinpakzad @Dev-iL @jroachgolf84 @seanghaeli @BentsiLeviav @koletzilla

Activity

  1. added
    kind:metaHigh-level information important to the community
    on Jun 19, 2026
  2. kacpermuda commented on Jun 19, 2026

    @kacpermuda
    Collaborator

    #68664 is ok, thanks !

  3. self-assigned this
    on Jun 19, 2026
  4. imrichardwu commented on Jun 19, 2026

    @imrichardwu
    Contributor

    #67586 LGTM

  5. fpopic commented on Jun 19, 2026

    @fpopic
    Contributor

    #68069 LGTM!

    Tested in real environment

    • Hashicorp Vault Enterprise v1.20.7
    • Managed Composer Airflow composer-2.16.11-airflow-2.11.1
  6. AlejandroMorgante commented on Jun 19, 2026

    @AlejandroMorgante
    Contributor

    Verified apache-airflow-providers-amazon[aiobotocore]==9.31.0rc1.

    Tested:
    #68140

    Environment:

    • Airflow 3.0.6 Docker environment
    • Python 3.12
    • Provider installed from the PyPI RC package
    • AWS region: us-east-1
    • Tested against a real Bedrock AgentCore Runtime in a test AWS account
    • Triggerer enabled

    Result:

    • Created a temporary AgentCore Runtime as test setup.
    • BedrockDeleteAgentRuntimeOperator(deferrable=True) submitted deletion, moved the task to
      DEFERRED, and resumed successfully from the triggerer.
    • The trigger fired TriggerEvent with status=success.
    • The runtime was confirmed deleted after AWS returned ResourceNotFoundException.
  7. pcorliss commented on Jun 19, 2026

    @pcorliss
    Contributor

    Verified #68100

    Tested in local breeze environment

  8. 23tae commented on Jun 21, 2026

    @23tae
    Contributor

    Tested #68292 in my local breeze env using unit tests. LGTM.

  9. litesh1998 commented on Jun 21, 2026

    @litesh1998
    Contributor

    Tested 68224, works fine

  10. Vamsi-klu commented on Jun 21, 2026

    @Vamsi-klu
  11. justinpakzad commented on Jun 21, 2026

    @justinpakzad
    Contributor

    #66642 is all good!

  12. SameerMesiah97 commented on Jun 21, 2026

    @SameerMesiah97
    Contributor

    apache-airflow-providers-cncf-kubernetes==10.18.1rc1
    PR #68507: This is a non-functional change. Unit tests should be sufficient.

    apache-airflow-providers-postgres==6.8.0rc1
    PR #67045: Changes are working as expected with no observed regressions.

  13. Dotify71 commented on Jun 21, 2026

    @Dotify71
    Contributor

    apache-airflow-providers-fab==3.7.0rc1
    PR #68162 & PR #68166: These are documentation-only changes to update FAB auth manager Flask config and FAB SSO guide for Airflow 3. No functional testing is required, and the changes are verified.

  14. vatsrahul1001 commented on Jun 22, 2026

    @vatsrahul1001
    Contributor

    KubernetesExecutor scheduler crashes with PicklingError on pod_override with kubernetes client 36.0 client. This is introduced in CNCF 10.18.0 version though where we bumped kubernetes client to 36 more details in issue #68827

  15. amoghrajesh commented on Jun 22, 2026

    @amoghrajesh
    Contributor

    Hello @shahar1 I would like to exclude spark from this wave, it contains these changes:

    #68067
    #67473

    which will be refactored / whose parameter will be renamed via this PR: #68623. Deferring the release will only avoid unwanted rename going in a release. As for breakage / backcompat, I am not worried cos the spark feature will really only be usable once 3.3 is released (it piggybacks on feature of 3.3 airflow - task state management), so I will let you use your judgement as to what to do here.

  16. shahar1 commented on Jun 22, 2026

    @shahar1
    ContributorAuthor

    Hello @shahar1 I would like to exclude spark from this wave, it contains these changes:

    #68067
    #67473

    which will be refactored / whose parameter will be renamed via this PR: #68623. Deferring the release will only avoid unwanted rename going in a release. As for breakage / backcompat, I am not worried cos the spark feature will really only be usable once 3.3 is released (it piggybacks on feature of 3.3 airflow - task state management), so I will let you use your judgement as to what to do here.

    Noted, thanks!
    Could you please also comment on the devlist?

  17. amoghrajesh commented on Jun 22, 2026

    @amoghrajesh
    Contributor

    Already done!

  18. potiuk commented on Jun 22, 2026

    @potiuk
    Member

    My changes look good.

  19. henry3260 commented on Jun 22, 2026

    @henry3260
    Contributor

    microsoft-azure 13.5.0rc1 - install + mocked
    PowerBIDatasetRefreshOperator wait_for_completion=False regression path OK

  20. bugraoz93 commented on Jun 22, 2026

    @bugraoz93
    Contributor

    My changes looks good, thanks Shahar!

  21. dabla commented on Jun 23, 2026

    @dabla
    Contributor

    Following changes looking good:

    #68321
    #67999
    #68375

  22. bugraoz93 commented on Jun 23, 2026

    @bugraoz93
    Contributor

    @shahar1 have you released providers? Can we hold fab, keycloak otherwise? checked they are released. Will reach out from broader audiance will tag you there

  23. molcay commented on Jun 26, 2026

    @molcay
    Contributor

    Hi everyone,

    Just a heads-up that the previous release candidate appears to have introduced a regression in apache-airflow-providers-cncf-kubernetes version 10.18.0 and this RC still contains the regression.

    We actually caught this while testing the apache-airflow-providers-google package. Since upgrading the Kubernetes provider, our tasks are failing with a 401 Unauthorized connection error when trying to authenticate with the cluster.

    For anyone else landing here while troubleshooting: downgrading to version 10.17.1 resolves the issue as a temporary workaround.

  24. shahar1 commented on Jun 26, 2026

    @shahar1
    ContributorAuthor

    Hi everyone,

    Just a heads-up that the previous release candidate appears to have introduced a regression in apache-airflow-providers-cncf-kubernetes version 10.18.0 and this RC still contains the regression.

    We actually caught this while testing the apache-airflow-providers-google package. Since upgrading the Kubernetes provider, our tasks are failing with a 401 Unauthorized connection error when trying to authenticate with the cluster.

    For anyone else landing here while troubleshooting: downgrading to version 10.17.1 resolves the issue as a temporary workaround.

    Thanks for reporting - I'll be happy if you could provide more details, and hopefully a PR to patch it.
    I'm currently working on an ad-hoc release, it would be best to include the fix there.

  25. amoghrajesh commented on Jun 29, 2026

    @amoghrajesh
    Contributor

    Apache spark changes look good.

  26. molcay commented on Jun 29, 2026

    @molcay
    Contributor

    Hi everyone,
    Just a heads-up that the previous release candidate appears to have introduced a regression in apache-airflow-providers-cncf-kubernetes version 10.18.0 and this RC still contains the regression.
    We actually caught this while testing the apache-airflow-providers-google package. Since upgrading the Kubernetes provider, our tasks are failing with a 401 Unauthorized connection error when trying to authenticate with the cluster.
    For anyone else landing here while troubleshooting: downgrading to version 10.17.1 resolves the issue as a temporary workaround.

    Thanks for reporting - I'll be happy if you could provide more details, and hopefully a PR to patch it. I'm currently working on an ad-hoc release, it would be best to include the fix there.

    I was trying to detect the problem on Friday; and saw your PR #69032 and thought that it was a fix for this. Because the issue #69023 was almost the problem that we faced. I will be running the all k8s system tests to check if they all OK now.

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

Metadata

Metadata

Assignees

Labels

area:providerskind:metaHigh-level information important to the communitytesting statusStatus of testing releases

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions