You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "jscheffl (via GitHub)" <gi...@apache.org> on 2026/05/19 21:39:51 UTC
[I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
jscheffl opened a new issue, #67213:
URL: https://github.com/apache/airflow/issues/67213
### 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 [airbyte: 5.5.0rc1](https://pypi.org/project/apache-airflow-providers-airbyte/5.5.0rc1)
- [ ] [Implement execution_timeout semantics for AirbyteTriggerSyncOperator in deferrable mode (#64051)](https://github.com/apache/airflow/pull/64051): @SameerMesiah97
Linked issues:
- [Linked Issue #61472](https://github.com/apache/airflow/pull/61472): @SameerMesiah97
## Provider [alibaba: 3.3.8rc1](https://pypi.org/project/apache-airflow-providers-alibaba/3.3.8rc1)
- [ ] [Fix Alibaba OSS provider: configurable endpoint and task handler log … (#66479)](https://github.com/apache/airflow/pull/66479): @hasangzc
## Provider [amazon: 9.29.0rc1](https://pypi.org/project/apache-airflow-providers-amazon/9.29.0rc1)
- [ ] [Add OpenLineage support to AthenaSQLHook (#66844)](https://github.com/apache/airflow/pull/66844): @rahul-madaan
- [ ] [Add S3TablesDeleteTableBucketPolicyOperator (#66957)](https://github.com/apache/airflow/pull/66957): @john-jac
- [ ] [Add OpenLineage parent and transport info injection to EmrContainerOperator (#66816)](https://github.com/apache/airflow/pull/66816): @rahul-madaan
Linked issues:
- [Linked Issue #64513](https://github.com/apache/airflow/pull/64513): @rahul-madaan
- [Linked Issue #64807](https://github.com/apache/airflow/pull/64807): @rahul-madaan
- [ ] [Add MwaaServerlessDeleteWorkflowOperator (#66891)](https://github.com/apache/airflow/pull/66891): @kars0508
- [ ] [feat: add callback support to aws batch executor (#62984)](https://github.com/apache/airflow/pull/62984): @dondaum
Linked issues:
- [Linked Issue #62887](https://github.com/apache/airflow/issues/62887): @ferruzzi
- [ ] [Add `MwaaServerlessUpdateWorkflowOperator` (#66833)](https://github.com/apache/airflow/pull/66833): @kars0508
- [ ] [Add `S3TablesPutTableBucketPolicyOperator` (#66720)](https://github.com/apache/airflow/pull/66720): @john-jac
- [ ] [Add `S3VectorsQueryVectorsOperator` (#66724)](https://github.com/apache/airflow/pull/66724): @john-jac
- [ ] [Adds async support to SageMakerNotebookJobTrigger (#65571)](https://github.com/apache/airflow/pull/65571): @Cloud-Architect-Emma
- [ ] [Add `S3VectorsPutVectorsOperator` (#66545)](https://github.com/apache/airflow/pull/66545): @john-jac
- [ ] [Add `S3TablesRenameTableOperator` (#66544)](https://github.com/apache/airflow/pull/66544): @john-jac
- [ ] [Add `MwaaServerlessStopWorkflowRunOperator` (#66548)](https://github.com/apache/airflow/pull/66548): @john-jac
- [ ] [Add `BedrockUpdateGuardrailOperator` (#66547)](https://github.com/apache/airflow/pull/66547): @john-jac
- [ ] [Add `GlueCatalogCreatePartitionOperator` (#66546)](https://github.com/apache/airflow/pull/66546): @john-jac
- [ ] [Add `MwaaServerlessWorkflowRunSensor` (#66382)](https://github.com/apache/airflow/pull/66382): @john-jac
- [ ] [Add `BedrockCreateEvaluationJobOperator` (#66722)](https://github.com/apache/airflow/pull/66722): @john-jac
- [ ] [Fix CreateWorkflowOperator if_exists=skip ARN construction (#66974)](https://github.com/apache/airflow/pull/66974): @kars0508
- [ ] [Fix EMR container job not cancelled on deferral timeout (#64770)](https://github.com/apache/airflow/pull/64770): @aurangzaib048
Linked issues:
- [Linked Issue #51883](https://github.com/apache/airflow/pull/51883): @dominikhei
- [Linked Issue #60517](https://github.com/apache/airflow/issues/60517): @arorasachin9
- [ ] [Add Bundle documentation for Amazon S3 and Google GCS providers (#66993)](https://github.com/apache/airflow/pull/66993): @shashbha14
Linked issues:
- [Linked Issue #66986](https://github.com/apache/airflow/issues/66986): @eladkal
## Provider [apache.kafka: 1.14.0rc1](https://pypi.org/project/apache-airflow-providers-apache-kafka/1.14.0rc1)
- [ ] [Fix KafkaError.name() called without parentheses in create_topic (#65734)](https://github.com/apache/airflow/pull/65734): @david-parkk
- [ ] [Fix AwaitMessageTrigger missing _task_instance attribute (#66302)](https://github.com/apache/airflow/pull/66302): @jason810496
Linked issues:
- [Linked Issue #64833](https://github.com/apache/airflow/pull/64833): @jason810496
## Provider [apache.livy: 4.5.6rc1](https://pypi.org/project/apache-airflow-providers-apache-livy/4.5.6rc1)
- [ ] [Include endpoint_prefix in LivyTrigger serialization (#66966)](https://github.com/apache/airflow/pull/66966): @Nishieee
Linked issues:
- [Linked Issue #66961](https://github.com/apache/airflow/issues/66961): @shahar1
## Provider [apache.spark: 6.0.2rc1](https://pypi.org/project/apache-airflow-providers-apache-spark/6.0.2rc1)
- [ ] [Fix SparkPipelinesHook for Spark Connect connections (#66498)](https://github.com/apache/airflow/pull/66498): @lisancao
## Provider [celery: 3.20.0rc1](https://pypi.org/project/apache-airflow-providers-celery/3.20.0rc1)
- [ ] [feat: add callback support to aws batch executor (#62984)](https://github.com/apache/airflow/pull/62984): @dondaum
Linked issues:
- [Linked Issue #62887](https://github.com/apache/airflow/issues/62887): @ferruzzi
## Provider [cncf.kubernetes: 10.17.1rc1](https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.17.1rc1)
- [ ] [Fix deferrable KPO trigger_reentry crash when pod is GC'd before re-entry (#66716)](https://github.com/apache/airflow/pull/66716): @jekeanyanwu
Linked issues:
- [Linked Issue #56976](https://github.com/apache/airflow/pull/56976): @m1racoli
- [Linked Issue #66715](https://github.com/apache/airflow/issues/66715): @jekeanyanwu
- [Linked Issue #39296](https://github.com/apache/airflow/pull/39296): @antoniocorralsierra
- [ ] [fix(k8s-executor): add latency + status metrics around pod API calls (#66806)](https://github.com/apache/airflow/pull/66806): @1fanwang
- [ ] [Re-defer KubernetesPodOperator when pod is still running after trigger error (#66705)](https://github.com/apache/airflow/pull/66705): @wolfdn
- [ ] [Fix KubernetesPodTrigger pod terminal state handling (#66650)](https://github.com/apache/airflow/pull/66650): @anmolxlight
- [ ] [Fix race condition in AsyncKubernetesHook corrupting global kubernetes_asyncio config (#65566)](https://github.com/apache/airflow/pull/65566): @ZhaoMJ
- [ ] [`fix/issue-66592`: Respecting `unwrap_single` for non-deferrable execution (#66596)](https://github.com/apache/airflow/pull/66596): @jroachgolf84
Linked issues:
- [Linked Issue #66592](https://github.com/apache/airflow/issues/66592): @farrukh-t
- [ ] [Fix kubernetes cleanup-pods ignoring --verbose (#65955)](https://github.com/apache/airflow/pull/65955): @henry3260
- [ ] [Preserve event resource version after empty sync polls (#66471)](https://github.com/apache/airflow/pull/66471): @hkc-8010
Linked issues:
- [Linked Issue #66470](https://github.com/apache/airflow/issues/66470): @hkc-8010
- [ ] [Fix SparkKubernetesOperator with deferrable=True falling through to KubernetesPodOperator.execute() creating a spurious pod (#66448)](https://github.com/apache/airflow/pull/66448): @Pranaykarvi
Linked issues:
- [Linked Issue #66437](https://github.com/apache/airflow/issues/66437): @nikhilkarve
- [ ] [KubernetesExecutor: scope periodic completed-pod adoption to dead schedulers (#66400)](https://github.com/apache/airflow/pull/66400): @potiuk
Linked issues:
- [Linked Issue #66396](https://github.com/apache/airflow/issues/66396): @potiuk
- [Linked Issue #61839](https://github.com/apache/airflow/pull/61839): @atrbgithub
## Provider [common.ai: 0.3.0rc1](https://pypi.org/project/apache-airflow-providers-common-ai/0.3.0rc1)
- [ ] [Add `LLMRetryPolicy` to common-ai provider (#65451)](https://github.com/apache/airflow/pull/65451): @kaxil
Linked issues:
- [Linked Issue #65474](https://github.com/apache/airflow/pull/65474): @kaxil
- [ ] [fix: update dependencies to fix dependabot alarms in providers.common.ai (#66628)](https://github.com/apache/airflow/pull/66628): @jscheffl
## Provider [common.compat: 1.15.0rc1](https://pypi.org/project/apache-airflow-providers-common-compat/1.15.0rc1)
- [ ] [Add BundleVersion dataclass and version_data persistence to DagVersion (#66491)](https://github.com/apache/airflow/pull/66491): @o-nikolas
## Provider [common.sql: 2.0.0rc1](https://pypi.org/project/apache-airflow-providers-common-sql/2.0.0rc1)
- [ ] [feat: Add standardized SQL check representation for listeners (#66849)](https://github.com/apache/airflow/pull/66849): @kacpermuda
## Provider [databricks: 7.15.0rc1](https://pypi.org/project/apache-airflow-providers-databricks/7.15.0rc1)
- [ ] [Databricks: support user-assigned managed identity for Azure VM auth (#66072)](https://github.com/apache/airflow/pull/66072): @sydongda
Linked issues:
- [Linked Issue #65588](https://github.com/apache/airflow/issues/65588): @sydongda
- [ ] [fix issue: #64828, repair missing job parameters if exists (#67055)](https://github.com/apache/airflow/pull/67055): @sydongda
Linked issues:
- [Linked Issue #64828](https://github.com/apache/airflow/issues/64828): @roydobbe
- [ ] [Preserve Databricks deferrable trigger caller across triggerer restarts (#66965)](https://github.com/apache/airflow/pull/66965): @Nishieee
Linked issues:
- [Linked Issue #66961](https://github.com/apache/airflow/issues/66961): @shahar1
- [ ] [Fix DatabricksWorkflowTaskGroup leaking TaskGroupContext on internal exception (#66582)](https://github.com/apache/airflow/pull/66582): @moomindani
Linked issues:
- [Linked Issue #55891](https://github.com/apache/airflow/pull/55891): @ayudovin
- [Linked Issue #42164](https://github.com/apache/airflow/issues/42164): @fedemgp
## Provider [dbt.cloud: 4.9.0rc1](https://pypi.org/project/apache-airflow-providers-dbt-cloud/4.9.0rc1)
- [ ] [Add DbtCloudListJobRunsOperator to DBT Cloud Provider (#66150)](https://github.com/apache/airflow/pull/66150): @SameerMesiah97
- [ ] [Refactor deferrable execution in DbtCloudRunJobOperator (#66449)](https://github.com/apache/airflow/pull/66449): @SameerMesiah97
Linked issues:
- [Linked Issue #64051](https://github.com/apache/airflow/pull/64051): @SameerMesiah97
## Provider [docker: 4.5.6rc1](https://pypi.org/project/apache-airflow-providers-docker/4.5.6rc1)
- [ ] [Fix DockerOperator init crash on dict mount entries (#66553)](https://github.com/apache/airflow/pull/66553): @bdsoha
Linked issues:
- [Linked Issue #52451](https://github.com/apache/airflow/pull/52451): @bdsoha
## Provider [edge3: 3.7.0rc1](https://pypi.org/project/apache-airflow-providers-edge3/3.7.0rc1)
- [ ] [Allow using fresh interpreter besides fork() in Edge Worker (#65943)](https://github.com/apache/airflow/pull/65943): @diogosilva30
Linked issues:
- [Linked Issue #65942](https://github.com/apache/airflow/issues/65942): @diogosilva30
- [ ] [Support BaseExecutor.run_workload() for Airflow 3.3 in Edge Worker (#65847)](https://github.com/apache/airflow/pull/65847): @jscheffl
- [ ] [Bugfix/make edge resilient against log errors (#66995)](https://github.com/apache/airflow/pull/66995): @jscheffl
- [ ] [Fix provider DB upgrades with existing tables (#66883)](https://github.com/apache/airflow/pull/66883): @anmolxlight
Linked issues:
- [Linked Issue #66674](https://github.com/apache/airflow/pull/66674): @anmolxlight
- [ ] [Refresh uv.lock and Edge OpenAPI spec after #67093 env upgrade (#67188)](https://github.com/apache/airflow/pull/67188): @vatsrahul1001
Linked issues:
- [Linked Issue #67174](https://github.com/apache/airflow/pull/67174): @jason810496
- [Linked Issue #67180](https://github.com/apache/airflow/pull/67180): @zachliu
- [Linked Issue #66574](https://github.com/apache/airflow/pull/66574): @potiuk
- [Linked Issue #67184](https://github.com/apache/airflow/pull/67184): @Lee-W
- [Linked Issue #67093](https://github.com/apache/airflow/pull/67093): @github-actions[bot]
- [Linked Issue #67130](https://github.com/apache/airflow/pull/67130): @bugraoz93
## Provider [elasticsearch: 6.5.4rc1](https://pypi.org/project/apache-airflow-providers-elasticsearch/6.5.4rc1)
- [ ] [ElasticsearchRemoteLogIO: Harden _parse_raw_log to handle malformed and non-JSON log lines (#66383)](https://github.com/apache/airflow/pull/66383): @SameerMesiah97
- [ ] [fix(elasticsearch): pin compatible-with at the transport layer to keep ES 8 servers working (#66065)](https://github.com/apache/airflow/pull/66065): @petercheon
Linked issues:
- [Linked Issue #66064](https://github.com/apache/airflow/pull/66064): @petercheon
- [Linked Issue #64070](https://github.com/apache/airflow/pull/64070): @Subham-KRLX
- [ ] [ElasticsearchSQLCursor: Implement fetchmany support (#66658)](https://github.com/apache/airflow/pull/66658): @SameerMesiah97
## Provider [fab: 3.6.4rc1](https://pypi.org/project/apache-airflow-providers-fab/3.6.4rc1)
- [ ] [Fix provider DB upgrades with existing tables (#66883)](https://github.com/apache/airflow/pull/66883): @anmolxlight
Linked issues:
- [Linked Issue #66674](https://github.com/apache/airflow/pull/66674): @anmolxlight
- [ ] [Fix FAB role deletion foreign key constraint violation (#66686)](https://github.com/apache/airflow/pull/66686): @kimjune01
Linked issues:
- [Linked Issue #65375](https://github.com/apache/airflow/issues/65375): @TKul6
- [ ] [Fix session cookie serialization when using securecookie backend (#66565)](https://github.com/apache/airflow/pull/66565): @smartlin5228
- [ ] [fix: the ldap authentication handler in the flask-ap... in override.py (#66417)](https://github.com/apache/airflow/pull/66417): @orbisai0security
- [ ] [Bump flask-appbuilder to 5.2.1 and mirror new auth event hooks (#66841)](https://github.com/apache/airflow/pull/66841): @potiuk
Linked issues:
- [Linked Issue #2440](https://github.com/apache/airflow/pull/2440): @abhijeetdhumal
- [Linked Issue #66840](https://github.com/apache/airflow/pull/66840): @potiuk
- [Linked Issue #2450](https://github.com/apache/airflow/pull/2450): @mdziemianko
- [Linked Issue #2451](https://github.com/apache/airflow/pull/2451): @lvicentesanchez
- [ ] [Pin pyjwt>=2.11.0 in FAB provider so flask_jwt_extended imports cleanly (#66840)](https://github.com/apache/airflow/pull/66840): @potiuk
Linked issues:
- [Linked Issue #61278](https://github.com/apache/airflow/pull/61278): @amoghrajesh
## Provider [git: 0.4.0rc1](https://pypi.org/project/apache-airflow-providers-git/0.4.0rc1)
- [ ] [Add Git Sparse Checkout to Git Dag Bundle (#67047)](https://github.com/apache/airflow/pull/67047): @jscheffl
- [ ] [Add BundleVersion dataclass and version_data persistence to DagVersion (#66491)](https://github.com/apache/airflow/pull/66491): @o-nikolas
## Provider [google: 22.0.0rc1](https://pypi.org/project/apache-airflow-providers-google/22.0.0rc1)
- [ ] [Remove MLEngine from google provider (#66526)](https://github.com/apache/airflow/pull/66526): @Crowiant
- [ ] [Add `host_key_policy` option to `ComputeEngineSSHHook` (#66746)](https://github.com/apache/airflow/pull/66746): @potiuk
- [ ] [Add BigQueryStreamingBufferEmptySensor for DML on streaming tables (#66652)](https://github.com/apache/airflow/pull/66652): @radhwene
Linked issues:
- [Linked Issue #59408](https://github.com/apache/airflow/issues/59408): @radhwene
- [Linked Issue #61148](https://github.com/apache/airflow/pull/61148): @radhwene
- [ ] [Delete unused job_id_path XCom push from BigQueryInsertJobOperator (#66760)](https://github.com/apache/airflow/pull/66760): @VladaZakharova
- [ ] [Migrate BigQueryInsertJobTrigger to use on_kill() for user-initiated kills (#66704)](https://github.com/apache/airflow/pull/66704): @kir-rin
Linked issues:
- [Linked Issue #65733](https://github.com/apache/airflow/issues/65733): @amoghrajesh
- [Linked Issue #65590](https://github.com/apache/airflow/pull/65590): @amoghrajesh
- [ ] [Add Cloud SQL Auth Proxy IAM authentication (#66510)](https://github.com/apache/airflow/pull/66510): @nailo2c
Linked issues:
- [Linked Issue #35347](https://github.com/apache/airflow/issues/35347): @jitendra390
- [ ] [Add aliases for rebranded Google services (#66344)](https://github.com/apache/airflow/pull/66344): @VladaZakharova
- [ ] [Add BigQuery routine operators and existence sensor (#65499)](https://github.com/apache/airflow/pull/65499): @alamashir
Linked issues:
- [Linked Issue #65467](https://github.com/apache/airflow/issues/65467): @alamashir
- [Linked Issue #47579](https://github.com/apache/airflow/issues/47579): @luke-hoffman1
- [ ] [Skip S3 folder-marker keys in S3ToGCSOperator (#65724)](https://github.com/apache/airflow/pull/65724): @yuseok89
- [ ] [Support all bq load job and ext table config options in GCSToBigQueryOperator (#64505)](https://github.com/apache/airflow/pull/64505): @mlauter
- [ ] [Preserve BigQueryIntervalCheckTrigger params after triggerer restart (#67053)](https://github.com/apache/airflow/pull/67053): @Vamsi-klu
Linked issues:
- [Linked Issue #66961](https://github.com/apache/airflow/issues/66961): @shahar1
- [ ] [Fix CloudRunExecuteJobOperator deferrable mode silently passing on cancel (#67050)](https://github.com/apache/airflow/pull/67050): @Vamsi-klu
Linked issues:
- [Linked Issue #57791](https://github.com/apache/airflow/issues/57791): @MarcusCramer91
- [ ] [Render Jinja templates in CloudBatchSubmitJobOperator job field (#67021)](https://github.com/apache/airflow/pull/67021): @nailo2c
Linked issues:
- [Linked Issue #37217](https://github.com/apache/airflow/issues/37217): @ya7010
- [ ] [Adapt GCP CloudSQL trigger to run in private cloud (#66917)](https://github.com/apache/airflow/pull/66917): @olegkachur-e
- [ ] [Serialize poll_interval and impersonation_chain on DataFusionStartPipelineTrigger (#66968)](https://github.com/apache/airflow/pull/66968): @Nishieee
Linked issues:
- [Linked Issue #66961](https://github.com/apache/airflow/issues/66961): @shahar1
- [ ] [Fix BigQueryStreamingBufferEmptySensor failing against real BigQuery (#66962)](https://github.com/apache/airflow/pull/66962): @shahar1
Linked issues:
- [Linked Issue #66963](https://github.com/apache/airflow/issues/66963): @shahar1
- [Linked Issue #66652](https://github.com/apache/airflow/pull/66652): @radhwene
- [ ] [Fix CloudSecretManagerBackend regression with explicit project_id (#61654)](https://github.com/apache/airflow/pull/61654): @dv-gorasiya
Linked issues:
- [Linked Issue #61217](https://github.com/apache/airflow/issues/61217): @kiranpreet-kaur17
- [ ] [Fix broken GKEStartPodOperator extra link (#66657)](https://github.com/apache/airflow/pull/66657): @Vamsi-klu
Linked issues:
- [Linked Issue #46658](https://github.com/apache/airflow/issues/46658): @mdering
- [ ] [Adjust GCP BigQuery triggers for the private cloud (#66404)](https://github.com/apache/airflow/pull/66404): @olegkachur-e
- [ ] [Add Bundle documentation for Amazon S3 and Google GCS providers (#66993)](https://github.com/apache/airflow/pull/66993): @shashbha14
Linked issues:
- [Linked Issue #66986](https://github.com/apache/airflow/issues/66986): @eladkal
- [ ] [Document Dataproc limitations in Sovereign Cloud from Google (#66706)](https://github.com/apache/airflow/pull/66706): @VladaZakharova
## Provider [imap: 3.11.3rc1](https://pypi.org/project/apache-airflow-providers-imap/3.11.3rc1)
- [ ] [Neutralize path separator in IMAP (#66951)](https://github.com/apache/airflow/pull/66951): @jscheffl
- [ ] [ImapHook: Handle mixed plaintext and RFC 2047 encoded attachment filenames (#66672)](https://github.com/apache/airflow/pull/66672): @SameerMesiah97
Linked issues:
- [Linked Issue #66578](https://github.com/apache/airflow/pull/66578): @mgustimz
- [Linked Issue #65875](https://github.com/apache/airflow/pull/65875): @MdSadiqMd
- [ ] [fix RFC 2047 filename decoding (#65875)](https://github.com/apache/airflow/pull/65875): @MdSadiqMd
Linked issues:
- [Linked Issue #65871](https://github.com/apache/airflow/issues/65871): @vaefremov95
## Provider [influxdb: 2.11.0rc1](https://pypi.org/project/apache-airflow-providers-influxdb/2.11.0rc1)
- [ ] [Add support for influx3 in influxdb provider (#58929)](https://github.com/apache/airflow/pull/58929): @arpitrathore
Linked issues:
- [Linked Issue #58610](https://github.com/apache/airflow/issues/58610): @arpitrathore
## Provider [keycloak: 0.7.2rc1](https://pypi.org/project/apache-airflow-providers-keycloak/0.7.2rc1)
- [ ] [Fix Keycloak default role policy wiring (#67031)](https://github.com/apache/airflow/pull/67031): @anmolxlight
Linked issues:
- [Linked Issue #67027](https://github.com/apache/airflow/issues/67027): @mogilevskiikonstantin-commits
- [ ] [Update Keycloak documentation to mention `[api] base_url` (#66023)](https://github.com/apache/airflow/pull/66023): @vincbeck
Linked issues:
- [Linked Issue #65952](https://github.com/apache/airflow/issues/65952): @n-badtke-cg
## Provider [microsoft.azure: 13.3.0rc1](https://pypi.org/project/apache-airflow-providers-microsoft-azure/13.3.0rc1)
- [ ] [Add deferrable mode to AzureContainerInstancesOperator (#62772)](https://github.com/apache/airflow/pull/62772): @cruseakshay
Linked issues:
- [Linked Issue #62433](https://github.com/apache/airflow/issues/62433): @tsanton
- [ ] [Fix Azure Batch provider import error by capping azure-batch<15 (#66452)](https://github.com/apache/airflow/pull/66452): @wjddn279
- [ ] [Fix error messages in `PythonVirtualenvOperator` when Azure Key Vault secret backend is configured (#67157)](https://github.com/apache/airflow/pull/67157): @wolfdn
## Provider [openlineage: 2.17.0rc1](https://pypi.org/project/apache-airflow-providers-openlineage/2.17.0rc1)
- [ ] [feat: Add standardized SQL check representation for listeners (#66849)](https://github.com/apache/airflow/pull/66849): @kacpermuda
- [ ] [cache connections in OpenLineage SQL hook lineage (#64843)](https://github.com/apache/airflow/pull/64843): @mobuchowski
## Provider [pinecone: 2.4.5rc1](https://pypi.org/project/apache-airflow-providers-pinecone/2.4.5rc1)
- [ ] [Stop passing `project_id` to the Pinecone client constructor (#66601)](https://github.com/apache/airflow/pull/66601): @potiuk
## Provider [sftp: 5.8.0rc1](https://pypi.org/project/apache-airflow-providers-sftp/5.8.0rc1)
- [ ] [SFTP: add async retrieve_file / store_file / mkdir to SFTPHookAsync and introduce SFTPClientPool (#64465)](https://github.com/apache/airflow/pull/64465): @dabla
## Provider [smtp: 3.0.1rc1](https://pypi.org/project/apache-airflow-providers-smtp/3.0.1rc1)
- [ ] [Fix smtp connection test for noop tuple response (#66406)](https://github.com/apache/airflow/pull/66406): @henry3260
Linked issues:
- [Linked Issue #66391](https://github.com/apache/airflow/issues/66391): @omacchioni
- [ ] [fix stmp email callback to use email_conn_id (#65072)](https://github.com/apache/airflow/pull/65072): @wjddn279
## Provider [snowflake: 6.13.0rc1](https://pypi.org/project/apache-airflow-providers-snowflake/6.13.0rc1)
- [ ] [Added statement timeout support in SnowflakeSqlApiHook & Operator (#63575)](https://github.com/apache/airflow/pull/63575): @justinpakzad
Linked issues:
- [Linked Issue #60894](https://github.com/apache/airflow/issues/60894): @HyunWooZZ
- [ ] [Replace AirflowExceptions with native exceptions in Snowflake provider (#66279)](https://github.com/apache/airflow/pull/66279): @justinpakzad
- [ ] [Add PAT connection to snowflake in SnowflakeHook docs (#66953)](https://github.com/apache/airflow/pull/66953): @romsharon98
- [ ] [Add Snowflake data quality operator examples to provider docs and system tests (#65623)](https://github.com/apache/airflow/pull/65623): @PrithviBadiga
Linked issues:
- [Linked Issue #65098](https://github.com/apache/airflow/issues/65098): @nagabharathnr
## Provider [standard: 1.13.1rc1](https://pypi.org/project/apache-airflow-providers-standard/1.13.1rc1)
- [ ] [fix: Handle `None` Task ID state when matching states in `ExternalTaskSensor` (#66881)](https://github.com/apache/airflow/pull/66881): @jroachgolf84
Linked issues:
- [Linked Issue #66877](https://github.com/apache/airflow/issues/66877): @nathadfield
- [ ] [Fix error messages in `PythonVirtualenvOperator` when Azure Key Vault secret backend is configured (#67157)](https://github.com/apache/airflow/pull/67157): @wolfdn
## Provider [tableau: 5.4.1rc1](https://pypi.org/project/apache-airflow-providers-tableau/5.4.1rc1)
- [ ] [Fix TableauOperator tasks.run AttributeError (#66682)](https://github.com/apache/airflow/pull/66682): @Vamsi-klu
Linked issues:
- [Linked Issue #42248](https://github.com/apache/airflow/issues/42248): @farrukh-t
## Provider [weaviate: 3.3.4rc1](https://pypi.org/project/apache-airflow-providers-weaviate/3.3.4rc1)
- [ ] [[main] Upgrade important CI environment (#66700)](https://github.com/apache/airflow/pull/66700): @github-actions[bot]
## Provider [zendesk: 4.12.0rc1](https://pypi.org/project/apache-airflow-providers-zendesk/4.12.0rc1)
- [ ] [Support API authentication for Zendesk (#64591)](https://github.com/apache/airflow/pull/64591): @Subham-KRLX
Linked issues:
- [Linked Issue #64589](https://github.com/apache/airflow/issues/64589): @fjmacagno
<!--
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:
@hasangzc @anmolxlight @PrithviBadiga @dabla @john-jac @jscheffl @moomindani @smartlin5228 @vatsrahul1001 @henry3260 @diogosilva30 @Pranaykarvi @Nishieee @kaxil @sydongda @jason810496 @kacpermuda @bdsoha @cruseakshay @shahar1 @mobuchowski @justinpakzad @kars0508 @wolfdn @aurangzaib048 @1fanwang @Vamsi-klu @Subham-KRLX @hkc-8010 @petercheon @kimjune01 @orbisai0security @vincbeck @nailo2c @dv-gorasiya @SameerMesiah97 @romsharon98 @MdSadiqMd @olegkachur-e @radhwe
### 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: commits-unsubscribe@airflow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "kacpermuda (via GitHub)" <gi...@apache.org>.
kacpermuda commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4498866965
Both my PRs are ok, tested my changes
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "nikhilkarve (via GitHub)" <gi...@apache.org>.
nikhilkarve commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4503587100
https://github.com/apache/airflow/pull/66448: @Pranaykarvi
Linked issues:
https://github.com/apache/airflow/issues/66437: @nikhilkarve
I have added my question in the comment of this PR. Can anyone please take a look at it?
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4518175354
> Oh damn! I missed that! Sorry about that. I agree for bumping to major version at this cycle, better later than never ...
I will finally have time soon to look at the agentic-driven changelog preparation, this should be something that the SKIIL we have for that should flag and detect automatically.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "SameerMesiah97 (via GitHub)" <gi...@apache.org>.
SameerMesiah97 commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4527985993
> > [@jscheffl](https://github.com/jscheffl) Is it possible to cut a second release candidate for the Airbyte and DBT Cloud providers in this release wave?
>
> I'd exclude Airbyte and DBT then from the wave release. I can make a RC2 if the fix landed on main before 2026-05-26, else it is making sense to "just skip" release and take it into next wave. [@SameerMesiah97](https://github.com/SameerMesiah97) would you be able to raise a fix PR before?
@jscheffl
I have opened 2 tightly scoped PRs to address the issues in both the Airbyte and DBT Cloud providers.. They are as follows:
Airbyte: PR #67382
DBT Cloud: PR #67360
They are very simple one line changes so I think they can be reviewed and merged before the deadline you stated.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "henry3260 (via GitHub)" <gi...@apache.org>.
henry3260 commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4506284510
Verified: #65955 and #66406 are working as expected.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "vincbeck (via GitHub)" <gi...@apache.org>.
vincbeck commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4509017255
> > [@jscheffl](https://github.com/jscheffl) Not that I have anything against, but why are we doing a major release of `common.sql`? I see only my feature PR since last release, and it's definitely not a breaking change.
>
> Oh, I needed a moment to triage backwards "how" this came. After a good sleep and a hard working day my memory is a bit dissolved from what I did yesterday but mechanics is as you nee in the published release notes of RC in https://airflow.staged.apache.org/docs/apache-airflow-providers-common-sql/2.0.0/changelog.html that there is a big fat warning banner about breaking change. This was in front of the changelog which by release manager mechanic the signal that a breaking change was added and this caused the major version bump.
>
> But as you hinted... looking at the history from past providers release from 2026-05-05 in https://github.com/apache/airflow/pull/66424/changes#diff-67507f2803366fd3ff09a384dcb696bfd4a20ab1e75bb3e15f289c63e37b18edR28 I need to acknowledge that re-reading the old state that by accident the braking change was actually missed 2 weeks ago in last providers release 1.36.0 - actually this would have needed to be 2.0.0.
>
> Due to the changelog and version mis-match... I assume it is fair to retro-major-bump the provider so that everybody in <= 1.36 sees there is a breaking change with warning. Would have been better last release cycle and this today we would have 2.1.0.
>
> Hope it is okay to keep 2.0.0 :-D
>
> (FYI [@vincbeck](https://github.com/vincbeck))
Oh damn! I missed that! Sorry about that. I agree for bumping to major version at this cycle, better later than never ...
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "VladaZakharova (via GitHub)" <gi...@apache.org>.
VladaZakharova commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4500003822
Google provider passed the tests
+1 for Google changes
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "Cloud-Architect-Emma (via GitHub)" <gi...@apache.org>.
Cloud-Architect-Emma commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4497142936
Verified apache-airflow-providers-amazon==9.29.0rc1 (#65571)
I verified that the `SageMakerNotebookJobTrigger` async implementation
is present and correct in the RC wheel:
- `SageMakerNotebookJobTrigger.run()` is now a proper async generator
using `asyncio.to_thread` for CI-safe async execution
- `serialize()` correctly round-trips all four fields: `execution_id`,
`execution_name`, `waiter_delay`, `waiter_max_attempts`
- Terminal success states (`COMPLETED`, `SUCCEEDED`) and failure states
(`FAILED`, `ERROR`, `CANCELLED`, `STOPPED`) are handled correctly
- Timeout behavior yields a `TriggerEvent` with `status: "failed"` and
`error: "Execution timed out"`
The implementation and all unit tests are present in the RC package.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "Subham-KRLX (via GitHub)" <gi...@apache.org>.
Subham-KRLX commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4494356282
Verified both Zendesk 4.12.0rc1 and Elasticsearch 6.5.4rc1. I ran the Zendesk unit tests covering the new API and OAuth token authentication paths and the UI connection behavior and they passed successfully. I also ran the Elasticsearch unit tests covering log ingestion index patterns and client compatibility and they all passed. Both look good to ship.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "petercheon (via GitHub)" <gi...@apache.org>.
petercheon commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4493279908
Verified **#66065 — fix(elasticsearch): pin compatible-with at the transport layer to keep ES 8 servers working** in `apache-airflow-providers-elasticsearch==6.5.4rc1`. ✅
### Environment
- Airflow `3.1.3` (clean venv, Python 3.11)
- `apache-airflow-providers-elasticsearch==6.5.4rc1` from PyPI
- `elasticsearch-py==9.4.0` (the default >=9 resolution that triggers the regression)
- Server: live Elasticsearch **8.17.3** cluster
### Steps
1. **Reproduced the regression first** (no fix applied): a raw `Elasticsearch(...)` client against the ES 8 server fails with the documented error —
```
BadRequestError(400, 'media_type_header_exception',
Accept version must be either version 8 or 7, but found 9.
Accept=application/vnd.elasticsearch+json; compatible-with=9)
```
2. **Applied the fix** by setting `AIRFLOW__ELASTICSEARCH__ES_COMPAT_WITH=8` and calling `airflow.providers.elasticsearch._compat.apply_compat_with(client)`. The following all succeed against the same ES 8 server:
- `client.info()` → `version.number = 8.17.3`
- `client.cluster.health()` → `status=green`
- `client.search(index="missing")` → clean 404 (no media-type error)
- `client.bulk(operations=...)` → `errors=False`, both docs indexed, `count=2`
3. **Wire-level confirmation** — swapped `elastic_transport.Transport.perform_request` for a spy and captured the headers actually sent:
```
info() Accept : application/vnd.elasticsearch+json; compatible-with=8
bulk() Accept : application/vnd.elasticsearch+json; compatible-with=8
bulk() Content-Type : application/vnd.elasticsearch+x-ndjson; compatible-with=8
```
The `+x-ndjson` Content-Type rewrite (the originally-broken bulk path) is correctly applied.
4. **End-to-end through the hook**: `ElasticsearchPythonHook` returns a client whose transport is wrapped when `es_compat_with` is set, and unwrapped when it isn't — same `hook.search(...)` call succeeds with the option set and fails with the 400 without it.
Looks good to ship from my side. 🎉
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "jscheffl (via GitHub)" <gi...@apache.org>.
jscheffl commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4502252449
> [@jscheffl](https://github.com/jscheffl) Not that I have anything against, but why are we doing a major release of `common.sql`? I see only my feature PR since last release, and it's definitely not a breaking change.
Oh, I needed a moment to triage backwards "how" this came. After a good sleep and a hard working day my memory is a bit dissolved from what I did yesterday but mechanics is as you nee in the published release notes of RC in https://airflow.staged.apache.org/docs/apache-airflow-providers-common-sql/2.0.0/changelog.html that there is a big fat warning banner about breaking change. This was in front of the changelog which by release manager mechanic the signal that a breaking change was added and this caused the major version bump.
But as you hinted... looking at the history from past providers release from 2026-05-05 in https://github.com/apache/airflow/pull/66424/changes#diff-67507f2803366fd3ff09a384dcb696bfd4a20ab1e75bb3e15f289c63e37b18edR28 I need to acknowledge that re-reading the old state that by accident the braking change was actually missed 2 weeks ago in last providers release 1.36.0 - actually this would have needed to be 2.0.0.
Due to the changelog and version mis-match... I assume it is fair to retro-major-bump the provider so that everybody in <= 1.36 sees there is a breaking change with warning. Would have been better last release cycle and this today we would have 2.1.0.
Hope it is okay to keep 2.0.0 :-D
(FYI @vincbeck)
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "Nishieee (via GitHub)" <gi...@apache.org>.
Nishieee commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4494619786
Hey!! I've verified the RC builds for my provider changes (installed from PyPI, tested via `.venv` imports from `site-packages`):
- **apache-airflow-providers-apache-livy==4.5.6rc1** ([#66966](https://github.com/apache/airflow/pull/66966)): `LivyTrigger` preserves `endpoint_prefix` through `serialize()` and restore.
- **apache-airflow-providers-databricks==7.15.0rc1** ([#66965](https://github.com/apache/airflow/pull/66965)): `caller` round-trips on `DatabricksExecutionTrigger` and `DatabricksSQLStatementExecutionTrigger`.
- **apache-airflow-providers-google==22.0.0rc1** ([#66968](https://github.com/apache/airflow/pull/66968)): `poll_interval` and `impersonation_chain` round-trip on `DataFusionStartPipelineTrigger`.
I don't have Livy, Databricks, or Data Fusion staging set up right now, so I couldn't run a full deferrable + triggerer-restart smoke test but the serialization checks against the RC wheels all passed on my side. If deeper integration testing would help, I'm glad to stand up environments and run those. just let me know.
Thanks!
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "jscheffl (via GitHub)" <gi...@apache.org>.
jscheffl commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4502596400
Also did some more testing with Edge Executor and Integration test Dag and all looks good.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "jscheffl (via GitHub)" <gi...@apache.org>.
jscheffl commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4524856764
> [@jscheffl](https://github.com/jscheffl) Is it possible to cut a second release candidate for the Airbyte and DBT Cloud providers in this release wave?
I'd exclude Airbyte and DBT then from the wave release. I can make a RC2 if the fix landed on main before 2026-05-26, else it is making sense to "just skip" release and take it into next wave. @SameerMesiah97 would you be able to raise a fix PR before?
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "david-parkk (via GitHub)" <gi...@apache.org>.
david-parkk commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4495945943
Verified apache-airflow-providers-apache-kafka==1.14.0rc1 (#65734)
**Environment**
- Airflow 3.2.1, Python 3.10, PostgreSQL
- apache-airflow-providers-apache-kafka==1.14.0rc1 from PyPI
**Steps**
- Installed the RC in Breeze and ran `kafka_exception_inspect` DAG against a live Kafka broker — specifically to verify the KafkaError.name() fix I contributed (#65734).
- Also run the unit tests (pytest providers/apache/kafka/tests/unit/apache/kafka/hooks/test_client.py -xvs)
thank you 😄
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "kacpermuda (via GitHub)" <gi...@apache.org>.
kacpermuda commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4506336525
Thanks @jscheffl for the detailed explanation, that indeed makes sense, did not think about checking previous version's PRs.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "kacpermuda (via GitHub)" <gi...@apache.org>.
kacpermuda commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4498486677
@jscheffl Not that I have anything against, but why are we doing a major release of `common.sql`? I see only my feature PR since last release, and it's definitely not a breaking change.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "zachliu (via GitHub)" <gi...@apache.org>.
zachliu commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4500551059
https://github.com/apache/airflow/pull/67180 passed the tests 🚀
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "jscheffl (via GitHub)" <gi...@apache.org>.
jscheffl commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4525567829
Thank you everyone. Providers are released.
I invite everyone to help improve providers for the next release, a list of open issues can be found [here](https://github.com/apache/airflow/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%3Aproviders).
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "sydongda (via GitHub)" <gi...@apache.org>.
sydongda commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4498918477
**Tested RC:** `apache-airflow-providers-databricks==7.15.0rc1`
**Related PRs: **#66072, #67055
### Test steps
1. Upgraded provider to `7.15.0rc1`
2. Created a Databricks connection using **user managed identity auth**
3. Created a DAG using the `job_parameters` param
4. First run – with `job_parameters`
- Checkpoint 1: connection to Databricks → ✅ **pass**
- Checkpoint 2: repair run with job_parameters → ✅ **pass**
5. Second run – without `job_parameters`
- Checkpoint: repair run without `job_parameters `→ ✅ **pass**
### Conclusion
✅ Both PRs (#66072, #67055) are addressed.
✅ No regressions observed for the tested scenarios.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "moomindani (via GitHub)" <gi...@apache.org>.
moomindani commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4497599231
Tested `apache-airflow-providers-databricks==7.15.0rc1` for PR #66582 (`DatabricksWorkflowTaskGroup` `TaskGroupContext` leak fix, closing #42164) — verification passes.
Installed the RC wheel into a fresh `apache-airflow==3.1.3` venv and ran the original reproducer from #42164: a `DatabricksWorkflowTaskGroup` with an `EmptyOperator` inside (which lacks `_convert_to_databricks_workflow_task` and therefore makes the workflow group's `__exit__` raise mid-way). With the RC installed:
- the expected `AirflowException: Task wf.not_convertible does not support conversion to databricks workflow task.` is raised,
- `TaskGroupContext._context` is empty afterwards (no leak), and
- a subsequent `DatabricksWorkflowTaskGroup` builds cleanly without the `Cannot mix TaskGroups from different DAGs` error that was the user-visible symptom on unfixed code.
Marking my line in the Databricks section.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "dondaum (via GitHub)" <gi...@apache.org>.
dondaum commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4496273772
#62984 looks good.
I have downloaded both RC versions for the amazon and celery providers. I can confirm that all relevant code changes are present.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "anmolxlight (via GitHub)" <gi...@apache.org>.
anmolxlight commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4507827966
Verified the RC wheels from PyPI for my provider changes.
Environment:
- Python 3.11.15
- apache-airflow==3.1.3
- apache-airflow-providers-cncf-kubernetes==10.17.1rc1
- apache-airflow-providers-edge3==3.7.0rc1
- apache-airflow-providers-fab==3.6.4rc1
- apache-airflow-providers-keycloak==0.7.2rc1
Checks performed:
- #66650 / cncf.kubernetes: verified `KubernetesPodTrigger` treats terminal pod phases as authoritative: `Succeeded` maps to success, `Failed` maps to failed even when the base container is still waiting, and non-terminal pods still fall back to base-container state. Also verified the trigger emits the expected failed event for a terminal failed pod.
- #66883 / edge3 and fab: verified provider DB managers handle existing provider tables without an Alembic version by stamping the base revision and then running migrations, while a genuinely empty DB still uses ORM table creation.
- #67031 / keycloak: verified default non-team role policies are created and attached to the generated permissions: `Allow-User`, `Allow-Op`, `Allow-Admin`, `Allow-SuperAdmin`, and the default team roles for `ReadOnly`.
All focused RC checks passed on my side.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "SameerMesiah97 (via GitHub)" <gi...@apache.org>.
SameerMesiah97 commented on issue #67213:
URL: https://github.com/apache/airflow/issues/67213#issuecomment-4513298790
`apache-airflow-providers-airbyte==5.5.0rc1`
PR #64051: During RC testing, it was discovered that the fix for issue #61472 is incomplete and the issue still persists. The cause appears to be that `self.execution_timeout` is still being passed to the `defer()` invocation in the operator. I’ll submit a follow-up PR with a fix.
`apache-airflow-providers-dbt-cloud==4.9.0rc1`
PR #66150: Changes are working as expected with no observed regressions.
PR #66449: Similar to PR #64051, a regression has been introduced by passing `self.execution_timeout` to the `defer()` invocation in the operator. I’ll submit a follow-up PR with a fix.
`apache-airflow-providers-elasticsearch==6.5.4rc1`
PR #66383: It is impractical to deterministically induce the emission of malformed logs so this rules out a quick sanity check against a real Elasticsearch cluster. However, the unit tests should be sufficient to ensure that the changes will work as expected.
PR #66658: Changes are working as expected with no observed regressions.
`apache-airflow-providers-imap==3.11.3rc1`
PR #66672: Changes are working as expected with no observed regressions.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Status of testing Providers that were prepared on May 19, 2026 [airflow]
Posted by "jscheffl (via GitHub)" <gi...@apache.org>.
jscheffl closed issue #67213: Status of testing Providers that were prepared on May 19, 2026
URL: https://github.com/apache/airflow/issues/67213
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org