You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Shahar Epstein <sh...@apache.org> on 2026/09/24 12:30:51 UTC

[VOTE] Airflow Providers, release preparation date 2026-09-22

Hey all,

I have just cut the new wave Airflow Providers packages with release
preparation date 2026-09-22. This email is calling a vote on the release,
which will last for an extended period of 5 days - which means that it will
end on 2026-09-29 12:00 UTC, with at least 3 binding +1 votes required for
the release to pass.

Consider this my (binding) +1.
General highlights

   - This wave includes many providers. Fun fact: there were so many that I
   had to split the testing GitHub issue in two! This is mainly due to the
   work on #35259, which adds connection ID templating across all providers.
   - Work on #70296 is nearly complete, with a few exceptions (in practice
   I resolved the issue). It moves template-field validation and
   transformation out of __init__ so they run after template rendering,
   preventing errors caused by processing unrendered values.
   - We hope to graduate common.ai to 1.0.0 in the next RC, whether in a
   wave or an ad hoc release. I'd like to ask the community's attention to
   test this provider’s 0.10.0 RC extensively, as it includes many changes.
   - To allow an appropriate time for testing all providers (in particular:
   common.ai, fab, google, and amazon) - I extend the usualy release vote
   period in extra two days than usual.

Breaking changes and upgrade notes

   - *edge3 4.3.2 → 5.0.0:* EdgeExecutor now counts queued workloads
   against [core] parallelism. Review this setting if you rely on higher
   concurrency (#72048).
   - *git 0.5.0 → 1.0.0:* Token authentication now uses a credential helper
   configured through GIT_CONFIG_COUNT and requires Git ≥ 2.31 on Dag
   processors and workers (#64105).
   - *microsoft.psrp 3.2.7 → 4.0.0:* PsrpOperator no longer defaults task_id
   to the cmdlet; pass task_id explicitly (#73036).
   - *openai 1.8.2 → 2.0.0:* create_embeddings now returns a list of
   embedding vectors for list inputs, rather than only the first vector. This
   also changes the XCom returned by OpenAIEmbeddingOperator for those
   inputs (#71989).
   - *common.ai <http://common.ai> 0.9.0 → 0.10.0:* PydanticAI vendor
   connection types change from hyphens to underscores; SQLToolset now
   rejects allowed_tables=None and allowed_tables=[] (omit the argument to
   allow all tables); and execute_complete overrides on LLMOperator and
   LLMBranchOperator must accept decision=None (#72853, #73381, #73452,
   #73368).
   - *Amazon:* Deferrable operators and sensors now pass their AWS region,
   TLS verification, and botocore settings to triggers (#72171). FTP/SFTP–S3
   transfers now match filename prefixes rather than substrings (#73269).

Deprecations

   - *Google Cloud Stackdriver:* Stackdriver components are renamed to
   Cloud Monitoring and Cloud Logging (#73354, #73575). The Stackdriver*
   operators, StackdriverHook, and Stackdriver links move to the new
   CloudMonitoring* classes in the cloud_monitoring modules. The
   Stackdriver task log handler becomes CloudLoggingTaskHandler in
   cloud_logging_task_handler. The old names still work but emit
   deprecation warnings; they are planned for removal after March 31, 2027.
   - *Google Cloud Pub/Sub:* The default for return_immediately is
   deprecated (#73504). PubSubPullOperator, PubSubPullSensor, and
   PubsubPullTrigger now warn when return_immediately is not set. This also
   applies to Google Pub/Sub asset watchers. The default will change from
   True to False in the first Google provider major release after March 31,
   2027. To preserve the current behavior, pass return_immediately=True.
   The deferrable PubSubPullSensor now respects this argument; previously,
   it dropped it, so the trigger always ran with True.
   - *Amazon QuickSight:* QuickSightHook.wait_for_state is deprecated in
   favor of wait_for_ingestion, and the operator’s check_interval is
   deprecated in favor of waiter_delay (#70218). No removal date has been
   set.



Airflow Providers are available at:
https://dist.apache.org/repos/dist/dev/airflow/providers/2026-09-22

*apache-airflow-providers-2026-09-22-source.tar.gz* is the full source
tarball of airflow repo - snapshot taken at the moment of provider's
release.

*apache-airflow-providers-<PROVIDER>-*.tar.gz* are the convenience python
"sdist" distributions that we publish in PyPI

*apache_airflow_providers_<PROVIDER>-*.whl are the convenience Python
"wheel" distributions that we publish in PyPI.

The test procedure for PMC members is described in
https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-pmc-members

The test procedure for and Contributors who would like to test this RC is
described in:
https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-contributors


Public keys are available at:
https://dist.apache.org/repos/dist/release/airflow/KEYS

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Only votes from PMC members are binding, but members of the community are
encouraged to test the release and vote with "(non-binding)".

Please note that the version number excludes the 'rcX' string.
This will allow us to rename the artifact without modifying
the artifact checksums when we actually release it.

The status of testing the providers by the community is kept here:
https://github.com/apache/airflow/issues/73658 - Part 1
https://github.com/apache/airflow/issues/73658#issuecomment-5813334599 -
Part 2

The issue is also the easiest way to see important PRs included in the RC
candidates.
Detailed changelog for the providers will be published in the documentation
after the
RC candidates are released.

You can find the RC packages in PyPI following these links:

https://pypi.org/project/apache-airflow-providers-airbyte/6.1.0rc1/
https://pypi.org/project/apache-airflow-providers-alibaba/3.5.0rc1/
https://pypi.org/project/apache-airflow-providers-amazon/9.37.0rc1/
https://pypi.org/project/apache-airflow-providers-anthropic/1.1.0rc1/
https://pypi.org/project/apache-airflow-providers-apache-beam/6.3.0rc1/
https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.10.0rc1/
https://pypi.org/project/apache-airflow-providers-apache-druid/4.6.0rc1/
https://pypi.org/project/apache-airflow-providers-apache-flink/1.9.0rc1/
https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.14.0rc1/
https://pypi.org/project/apache-airflow-providers-apache-hive/9.7.0rc1/
https://pypi.org/project/apache-airflow-providers-apache-kylin/3.11.0rc1/
https://pypi.org/project/apache-airflow-providers-apache-livy/4.6.2rc1/
https://pypi.org/project/apache-airflow-providers-apache-pig/4.9.0rc1/
https://pypi.org/project/apache-airflow-providers-apache-tinkerpop/1.2.0rc1/
https://pypi.org/project/apache-airflow-providers-apprise/2.4.0rc1/
https://pypi.org/project/apache-airflow-providers-arangodb/2.10.0rc1/
https://pypi.org/project/apache-airflow-providers-asana/2.12.0rc1/
https://pypi.org/project/apache-airflow-providers-atlassian-jira/3.4.0rc1/
https://pypi.org/project/apache-airflow-providers-celery/3.24.1rc1/
https://pypi.org/project/apache-airflow-providers-cloudant/4.3.6rc1/
https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.23.0rc1/
https://pypi.org/project/apache-airflow-providers-cohere/1.8.0rc1/
https://pypi.org/project/apache-airflow-providers-common-ai/0.10.0rc1/
https://pypi.org/project/apache-airflow-providers-common-compat/1.20.0rc1/
https://pypi.org/project/apache-airflow-providers-common-io/1.10.0rc1/
https://pypi.org/project/apache-airflow-providers-common-messaging/2.1.1rc1/
https://pypi.org/project/apache-airflow-providers-common-sql/2.2.0rc1/
https://pypi.org/project/apache-airflow-providers-databricks/7.21.0rc1/
https://pypi.org/project/apache-airflow-providers-datadog/3.11.0rc1/
https://pypi.org/project/apache-airflow-providers-dbt-cloud/4.10.0rc1/
https://pypi.org/project/apache-airflow-providers-dingding/3.10.0rc1/
https://pypi.org/project/apache-airflow-providers-docker/4.6.0rc1/
https://pypi.org/project/apache-airflow-providers-duckdb/0.1.0rc1/
https://pypi.org/project/apache-airflow-providers-edge3/5.0.0rc1/
https://pypi.org/project/apache-airflow-providers-exasol/4.11.0rc1/
https://pypi.org/project/apache-airflow-providers-fab/3.10.0rc1/
https://pypi.org/project/apache-airflow-providers-ftp/3.16.0rc1/
https://pypi.org/project/apache-airflow-providers-git/1.0.0rc1/
https://pypi.org/project/apache-airflow-providers-github/2.12.0rc1/
https://pypi.org/project/apache-airflow-providers-google/22.6.0rc1/
https://pypi.org/project/apache-airflow-providers-grpc/3.10.0rc1/
https://pypi.org/project/apache-airflow-providers-hashicorp/4.8.2rc1/
https://pypi.org/project/apache-airflow-providers-http/6.2.0rc1/
https://pypi.org/project/apache-airflow-providers-imap/3.13.0rc1/
https://pypi.org/project/apache-airflow-providers-influxdb/2.12.0rc1/
https://pypi.org/project/apache-airflow-providers-keycloak/0.11.0rc1/
https://pypi.org/project/apache-airflow-providers-microsoft-azure/15.2.0rc1/
https://pypi.org/project/apache-airflow-providers-microsoft-psrp/4.0.0rc1/
https://pypi.org/project/apache-airflow-providers-microsoft-winrm/3.15.0rc1/
https://pypi.org/project/apache-airflow-providers-mongo/5.5.0rc1/
https://pypi.org/project/apache-airflow-providers-mysql/6.7.0rc1/
https://pypi.org/project/apache-airflow-providers-neo4j/3.13.0rc1/
https://pypi.org/project/apache-airflow-providers-openai/2.0.0rc1/
https://pypi.org/project/apache-airflow-providers-openlineage/2.20.2rc1/
https://pypi.org/project/apache-airflow-providers-opensearch/1.13.0rc1/
https://pypi.org/project/apache-airflow-providers-opsgenie/5.11.0rc1/
https://pypi.org/project/apache-airflow-providers-oracle/4.7.0rc1/
https://pypi.org/project/apache-airflow-providers-pagerduty/5.3.0rc1/
https://pypi.org/project/apache-airflow-providers-pinecone/2.5.0rc1/
https://pypi.org/project/apache-airflow-providers-postgres/7.1.0rc1/
https://pypi.org/project/apache-airflow-providers-presto/5.13.0rc1/
https://pypi.org/project/apache-airflow-providers-qdrant/1.6.0rc1/
https://pypi.org/project/apache-airflow-providers-redis/4.7.0rc1/
https://pypi.org/project/apache-airflow-providers-salesforce/5.15.0rc1/
https://pypi.org/project/apache-airflow-providers-samba/4.14.0rc1/
https://pypi.org/project/apache-airflow-providers-segment/3.10.0rc1/
https://pypi.org/project/apache-airflow-providers-sftp/6.1.0rc1/
https://pypi.org/project/apache-airflow-providers-slack/9.11.0rc1/
https://pypi.org/project/apache-airflow-providers-smtp/3.1.0rc1/
https://pypi.org/project/apache-airflow-providers-snowflake/6.18.0rc1/
https://pypi.org/project/apache-airflow-providers-ssh/6.1.0rc1/
https://pypi.org/project/apache-airflow-providers-standard/1.20.0rc1/
https://pypi.org/project/apache-airflow-providers-tableau/5.7.0rc1/
https://pypi.org/project/apache-airflow-providers-telegram/4.10.0rc1/
https://pypi.org/project/apache-airflow-providers-teradata/3.7.0rc1/
https://pypi.org/project/apache-airflow-providers-trino/6.7.0rc1/
https://pypi.org/project/apache-airflow-providers-weaviate/3.5.0rc1/
https://pypi.org/project/apache-airflow-providers-yandex/4.6.0rc1/

Sincerely,
Shahar Epstein

Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Aaron Chen <na...@gmail.com>.
+1 (non-binding)

Tested the providers I contributed to in this wave, and they look good.

https://pypi.org/project/apache-airflow-providers-amazon/9.37.0rc1/
https://pypi.org/project/apache-airflow-providers-google/22.6.0rc1/
https://pypi.org/project/apache-airflow-providers-microsoft-azure/15.2.0rc1/

Best,
Aaron

On Thu, Sep 24, 2026 at 5:33 AM Shahar Epstein <sh...@apache.org> wrote:

> Hey all,
>
> I have just cut the new wave Airflow Providers packages with release
> preparation date 2026-09-22. This email is calling a vote on the release,
> which will last for an extended period of 5 days - which means that it will
> end on 2026-09-29 12:00 UTC, with at least 3 binding +1 votes required for
> the release to pass.
>
> Consider this my (binding) +1.
> General highlights
>
>    - This wave includes many providers. Fun fact: there were so many that I
>    had to split the testing GitHub issue in two! This is mainly due to the
>    work on #35259, which adds connection ID templating across all
> providers.
>    - Work on #70296 is nearly complete, with a few exceptions (in practice
>    I resolved the issue). It moves template-field validation and
>    transformation out of __init__ so they run after template rendering,
>    preventing errors caused by processing unrendered values.
>    - We hope to graduate common.ai to 1.0.0 in the next RC, whether in a
>    wave or an ad hoc release. I'd like to ask the community's attention to
>    test this provider’s 0.10.0 RC extensively, as it includes many changes.
>    - To allow an appropriate time for testing all providers (in particular:
>    common.ai, fab, google, and amazon) - I extend the usualy release vote
>    period in extra two days than usual.
>
> Breaking changes and upgrade notes
>
>    - *edge3 4.3.2 → 5.0.0:* EdgeExecutor now counts queued workloads
>    against [core] parallelism. Review this setting if you rely on higher
>    concurrency (#72048).
>    - *git 0.5.0 → 1.0.0:* Token authentication now uses a credential helper
>    configured through GIT_CONFIG_COUNT and requires Git ≥ 2.31 on Dag
>    processors and workers (#64105).
>    - *microsoft.psrp 3.2.7 → 4.0.0:* PsrpOperator no longer defaults
> task_id
>    to the cmdlet; pass task_id explicitly (#73036).
>    - *openai 1.8.2 → 2.0.0:* create_embeddings now returns a list of
>    embedding vectors for list inputs, rather than only the first vector.
> This
>    also changes the XCom returned by OpenAIEmbeddingOperator for those
>    inputs (#71989).
>    - *common.ai <http://common.ai> 0.9.0 → 0.10.0:* PydanticAI vendor
>    connection types change from hyphens to underscores; SQLToolset now
>    rejects allowed_tables=None and allowed_tables=[] (omit the argument to
>    allow all tables); and execute_complete overrides on LLMOperator and
>    LLMBranchOperator must accept decision=None (#72853, #73381, #73452,
>    #73368).
>    - *Amazon:* Deferrable operators and sensors now pass their AWS region,
>    TLS verification, and botocore settings to triggers (#72171).
> FTP/SFTP–S3
>    transfers now match filename prefixes rather than substrings (#73269).
>
> Deprecations
>
>    - *Google Cloud Stackdriver:* Stackdriver components are renamed to
>    Cloud Monitoring and Cloud Logging (#73354, #73575). The Stackdriver*
>    operators, StackdriverHook, and Stackdriver links move to the new
>    CloudMonitoring* classes in the cloud_monitoring modules. The
>    Stackdriver task log handler becomes CloudLoggingTaskHandler in
>    cloud_logging_task_handler. The old names still work but emit
>    deprecation warnings; they are planned for removal after March 31, 2027.
>    - *Google Cloud Pub/Sub:* The default for return_immediately is
>    deprecated (#73504). PubSubPullOperator, PubSubPullSensor, and
>    PubsubPullTrigger now warn when return_immediately is not set. This also
>    applies to Google Pub/Sub asset watchers. The default will change from
>    True to False in the first Google provider major release after March 31,
>    2027. To preserve the current behavior, pass return_immediately=True.
>    The deferrable PubSubPullSensor now respects this argument; previously,
>    it dropped it, so the trigger always ran with True.
>    - *Amazon QuickSight:* QuickSightHook.wait_for_state is deprecated in
>    favor of wait_for_ingestion, and the operator’s check_interval is
>    deprecated in favor of waiter_delay (#70218). No removal date has been
>    set.
>
>
>
> Airflow Providers are available at:
> https://dist.apache.org/repos/dist/dev/airflow/providers/2026-09-22
>
> *apache-airflow-providers-2026-09-22-source.tar.gz* is the full source
> tarball of airflow repo - snapshot taken at the moment of provider's
> release.
>
> *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the convenience python
> "sdist" distributions that we publish in PyPI
>
> *apache_airflow_providers_<PROVIDER>-*.whl are the convenience Python
> "wheel" distributions that we publish in PyPI.
>
> The test procedure for PMC members is described in
>
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-pmc-members
>
> The test procedure for and Contributors who would like to test this RC is
> described in:
>
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-contributors
>
>
> Public keys are available at:
> https://dist.apache.org/repos/dist/release/airflow/KEYS
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Only votes from PMC members are binding, but members of the community are
> encouraged to test the release and vote with "(non-binding)".
>
> Please note that the version number excludes the 'rcX' string.
> This will allow us to rename the artifact without modifying
> the artifact checksums when we actually release it.
>
> The status of testing the providers by the community is kept here:
> https://github.com/apache/airflow/issues/73658 - Part 1
> https://github.com/apache/airflow/issues/73658#issuecomment-5813334599 -
> Part 2
>
> The issue is also the easiest way to see important PRs included in the RC
> candidates.
> Detailed changelog for the providers will be published in the documentation
> after the
> RC candidates are released.
>
> You can find the RC packages in PyPI following these links:
>
> https://pypi.org/project/apache-airflow-providers-airbyte/6.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-alibaba/3.5.0rc1/
> https://pypi.org/project/apache-airflow-providers-amazon/9.37.0rc1/
> https://pypi.org/project/apache-airflow-providers-anthropic/1.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-beam/6.3.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-druid/4.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-flink/1.9.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.14.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-hive/9.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-kylin/3.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-livy/4.6.2rc1/
> https://pypi.org/project/apache-airflow-providers-apache-pig/4.9.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-apache-tinkerpop/1.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-apprise/2.4.0rc1/
> https://pypi.org/project/apache-airflow-providers-arangodb/2.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-asana/2.12.0rc1/
> https://pypi.org/project/apache-airflow-providers-atlassian-jira/3.4.0rc1/
> https://pypi.org/project/apache-airflow-providers-celery/3.24.1rc1/
> https://pypi.org/project/apache-airflow-providers-cloudant/4.3.6rc1/
>
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.23.0rc1/
> https://pypi.org/project/apache-airflow-providers-cohere/1.8.0rc1/
> https://pypi.org/project/apache-airflow-providers-common-ai/0.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-common-compat/1.20.0rc1/
> https://pypi.org/project/apache-airflow-providers-common-io/1.10.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-common-messaging/2.1.1rc1/
> https://pypi.org/project/apache-airflow-providers-common-sql/2.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-databricks/7.21.0rc1/
> https://pypi.org/project/apache-airflow-providers-datadog/3.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-dbt-cloud/4.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-dingding/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-docker/4.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-duckdb/0.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-edge3/5.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-exasol/4.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-fab/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-ftp/3.16.0rc1/
> https://pypi.org/project/apache-airflow-providers-git/1.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-github/2.12.0rc1/
> https://pypi.org/project/apache-airflow-providers-google/22.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-grpc/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-hashicorp/4.8.2rc1/
> https://pypi.org/project/apache-airflow-providers-http/6.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-imap/3.13.0rc1/
> https://pypi.org/project/apache-airflow-providers-influxdb/2.12.0rc1/
> https://pypi.org/project/apache-airflow-providers-keycloak/0.11.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-microsoft-azure/15.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-microsoft-psrp/4.0.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-microsoft-winrm/3.15.0rc1/
> https://pypi.org/project/apache-airflow-providers-mongo/5.5.0rc1/
> https://pypi.org/project/apache-airflow-providers-mysql/6.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-neo4j/3.13.0rc1/
> https://pypi.org/project/apache-airflow-providers-openai/2.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-openlineage/2.20.2rc1/
> https://pypi.org/project/apache-airflow-providers-opensearch/1.13.0rc1/
> https://pypi.org/project/apache-airflow-providers-opsgenie/5.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-oracle/4.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-pagerduty/5.3.0rc1/
> https://pypi.org/project/apache-airflow-providers-pinecone/2.5.0rc1/
> https://pypi.org/project/apache-airflow-providers-postgres/7.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-presto/5.13.0rc1/
> https://pypi.org/project/apache-airflow-providers-qdrant/1.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-redis/4.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-salesforce/5.15.0rc1/
> https://pypi.org/project/apache-airflow-providers-samba/4.14.0rc1/
> https://pypi.org/project/apache-airflow-providers-segment/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-sftp/6.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-slack/9.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-smtp/3.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-snowflake/6.18.0rc1/
> https://pypi.org/project/apache-airflow-providers-ssh/6.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-standard/1.20.0rc1/
> https://pypi.org/project/apache-airflow-providers-tableau/5.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-telegram/4.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-teradata/3.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-trino/6.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-weaviate/3.5.0rc1/
> https://pypi.org/project/apache-airflow-providers-yandex/4.6.0rc1/
>
> Sincerely,
> Shahar Epstein
>

Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Shahar Epstein <sh...@apache.org>.
Almost missed out this one -

-1 (binding) for cncf.kubernetes due to a regression that was fixed here:
https://github.com/apache/airflow/pull/73764
Thanks to Anish Giri for pointing it out :)


Shahar

On Mon, Sep 28, 2026 at 11:00 PM Shahar Epstein <sh...@apache.org> wrote:

> Hey everyone,
>
> First - I'd like to thank everyone who has participated so far in testing
> and voting, both on the devlist as well as the GitHub issue!
> Second, due to some personal circumstances, I'll have to end the extended
> vote earlier than planned, and start publishing the release around
> 2026-09-29 06:00 UTC.
> Currently, only the edge provider is excluded from the release. If you
> find justified reasons to exclude other providers, please cast your -1 vote
> in the thread at earliest convenience.
>
> Thank you for your understanding and cooperation!
>
>
> Shahar
>
> On Thu, Sep 24, 2026 at 3:30 PM Shahar Epstein <sh...@apache.org> wrote:
>
>> Hey all,
>>
>> I have just cut the new wave Airflow Providers packages with release
>> preparation date 2026-09-22. This email is calling a vote on the release,
>> which will last for an extended period of 5 days - which means that it
>> will end on 2026-09-29 12:00 UTC, with at least 3 binding +1 votes required
>> for the release to pass.
>>
>> Consider this my (binding) +1.
>> General highlights
>>
>>    - This wave includes many providers. Fun fact: there were so many
>>    that I had to split the testing GitHub issue in two! This is mainly due to
>>    the work on #35259, which adds connection ID templating across all
>>    providers.
>>    - Work on #70296 is nearly complete, with a few exceptions (in
>>    practice I resolved the issue). It moves template-field validation and
>>    transformation out of __init__ so they run after template rendering,
>>    preventing errors caused by processing unrendered values.
>>    - We hope to graduate common.ai to 1.0.0 in the next RC, whether in a
>>    wave or an ad hoc release. I'd like to ask the community's attention to
>>    test this provider’s 0.10.0 RC extensively, as it includes many changes.
>>    - To allow an appropriate time for testing all providers (in
>>    particular: common.ai, fab, google, and amazon) - I extend the usualy
>>    release vote period in extra two days than usual.
>>
>> Breaking changes and upgrade notes
>>
>>    - *edge3 4.3.2 → 5.0.0:* EdgeExecutor now counts queued workloads
>>    against [core] parallelism. Review this setting if you rely on higher
>>    concurrency (#72048).
>>    - *git 0.5.0 → 1.0.0:* Token authentication now uses a credential
>>    helper configured through GIT_CONFIG_COUNT and requires Git ≥ 2.31 on
>>    Dag processors and workers (#64105).
>>    - *microsoft.psrp 3.2.7 → 4.0.0:* PsrpOperator no longer defaults
>>    task_id to the cmdlet; pass task_id explicitly (#73036).
>>    - *openai 1.8.2 → 2.0.0:* create_embeddings now returns a list of
>>    embedding vectors for list inputs, rather than only the first vector. This
>>    also changes the XCom returned by OpenAIEmbeddingOperator for those
>>    inputs (#71989).
>>    - *common.ai <http://common.ai> 0.9.0 → 0.10.0:* PydanticAI vendor
>>    connection types change from hyphens to underscores; SQLToolset now
>>    rejects allowed_tables=None and allowed_tables=[] (omit the argument
>>    to allow all tables); and execute_complete overrides on LLMOperator
>>    and LLMBranchOperator must accept decision=None (#72853, #73381,
>>    #73452, #73368).
>>    - *Amazon:* Deferrable operators and sensors now pass their AWS
>>    region, TLS verification, and botocore settings to triggers (#72171).
>>    FTP/SFTP–S3 transfers now match filename prefixes rather than substrings
>>    (#73269).
>>
>> Deprecations
>>
>>    - *Google Cloud Stackdriver:* Stackdriver components are renamed to
>>    Cloud Monitoring and Cloud Logging (#73354, #73575). The Stackdriver*
>>    operators, StackdriverHook, and Stackdriver links move to the new
>>    CloudMonitoring* classes in the cloud_monitoring modules. The
>>    Stackdriver task log handler becomes CloudLoggingTaskHandler in
>>    cloud_logging_task_handler. The old names still work but emit
>>    deprecation warnings; they are planned for removal after March 31, 2027.
>>    - *Google Cloud Pub/Sub:* The default for return_immediately is
>>    deprecated (#73504). PubSubPullOperator, PubSubPullSensor, and
>>    PubsubPullTrigger now warn when return_immediately is not set. This
>>    also applies to Google Pub/Sub asset watchers. The default will change from
>>    True to False in the first Google provider major release after March
>>    31, 2027. To preserve the current behavior, pass
>>    return_immediately=True. The deferrable PubSubPullSensor now respects
>>    this argument; previously, it dropped it, so the trigger always ran with
>>    True.
>>    - *Amazon QuickSight:* QuickSightHook.wait_for_state is deprecated in
>>    favor of wait_for_ingestion, and the operator’s check_interval is
>>    deprecated in favor of waiter_delay (#70218). No removal date has
>>    been set.
>>
>>
>>
>> Airflow Providers are available at:
>> https://dist.apache.org/repos/dist/dev/airflow/providers/2026-09-22
>>
>> *apache-airflow-providers-2026-09-22-source.tar.gz* is the full source
>> tarball of airflow repo - snapshot taken at the moment of provider's
>> release.
>>
>> *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the convenience python
>> "sdist" distributions that we publish in PyPI
>>
>> *apache_airflow_providers_<PROVIDER>-*.whl are the convenience Python
>> "wheel" distributions that we publish in PyPI.
>>
>> The test procedure for PMC members is described in
>>
>> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-pmc-members
>>
>> The test procedure for and Contributors who would like to test this RC is
>> described in:
>>
>> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-contributors
>>
>>
>> Public keys are available at:
>> https://dist.apache.org/repos/dist/release/airflow/KEYS
>>
>> Please vote accordingly:
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove with the reason
>>
>> Only votes from PMC members are binding, but members of the community are
>> encouraged to test the release and vote with "(non-binding)".
>>
>> Please note that the version number excludes the 'rcX' string.
>> This will allow us to rename the artifact without modifying
>> the artifact checksums when we actually release it.
>>
>> The status of testing the providers by the community is kept here:
>> https://github.com/apache/airflow/issues/73658 - Part 1
>> https://github.com/apache/airflow/issues/73658#issuecomment-5813334599 -
>> Part 2
>>
>> The issue is also the easiest way to see important PRs included in the RC
>> candidates.
>> Detailed changelog for the providers will be published in the
>> documentation after the
>> RC candidates are released.
>>
>> You can find the RC packages in PyPI following these links:
>>
>> https://pypi.org/project/apache-airflow-providers-airbyte/6.1.0rc1/
>> https://pypi.org/project/apache-airflow-providers-alibaba/3.5.0rc1/
>> https://pypi.org/project/apache-airflow-providers-amazon/9.37.0rc1/
>> https://pypi.org/project/apache-airflow-providers-anthropic/1.1.0rc1/
>> https://pypi.org/project/apache-airflow-providers-apache-beam/6.3.0rc1/
>>
>> https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.10.0rc1/
>> https://pypi.org/project/apache-airflow-providers-apache-druid/4.6.0rc1/
>> https://pypi.org/project/apache-airflow-providers-apache-flink/1.9.0rc1/
>> https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.14.0rc1/
>> https://pypi.org/project/apache-airflow-providers-apache-hive/9.7.0rc1/
>> https://pypi.org/project/apache-airflow-providers-apache-kylin/3.11.0rc1/
>> https://pypi.org/project/apache-airflow-providers-apache-livy/4.6.2rc1/
>> https://pypi.org/project/apache-airflow-providers-apache-pig/4.9.0rc1/
>>
>> https://pypi.org/project/apache-airflow-providers-apache-tinkerpop/1.2.0rc1/
>> https://pypi.org/project/apache-airflow-providers-apprise/2.4.0rc1/
>> https://pypi.org/project/apache-airflow-providers-arangodb/2.10.0rc1/
>> https://pypi.org/project/apache-airflow-providers-asana/2.12.0rc1/
>> https://pypi.org/project/apache-airflow-providers-atlassian-jira/3.4.0rc1/
>> https://pypi.org/project/apache-airflow-providers-celery/3.24.1rc1/
>> https://pypi.org/project/apache-airflow-providers-cloudant/4.3.6rc1/
>>
>> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.23.0rc1/
>> https://pypi.org/project/apache-airflow-providers-cohere/1.8.0rc1/
>> https://pypi.org/project/apache-airflow-providers-common-ai/0.10.0rc1/
>> https://pypi.org/project/apache-airflow-providers-common-compat/1.20.0rc1/
>> https://pypi.org/project/apache-airflow-providers-common-io/1.10.0rc1/
>>
>> https://pypi.org/project/apache-airflow-providers-common-messaging/2.1.1rc1/
>> https://pypi.org/project/apache-airflow-providers-common-sql/2.2.0rc1/
>> https://pypi.org/project/apache-airflow-providers-databricks/7.21.0rc1/
>> https://pypi.org/project/apache-airflow-providers-datadog/3.11.0rc1/
>> https://pypi.org/project/apache-airflow-providers-dbt-cloud/4.10.0rc1/
>> https://pypi.org/project/apache-airflow-providers-dingding/3.10.0rc1/
>> https://pypi.org/project/apache-airflow-providers-docker/4.6.0rc1/
>> https://pypi.org/project/apache-airflow-providers-duckdb/0.1.0rc1/
>> https://pypi.org/project/apache-airflow-providers-edge3/5.0.0rc1/
>> https://pypi.org/project/apache-airflow-providers-exasol/4.11.0rc1/
>> https://pypi.org/project/apache-airflow-providers-fab/3.10.0rc1/
>> https://pypi.org/project/apache-airflow-providers-ftp/3.16.0rc1/
>> https://pypi.org/project/apache-airflow-providers-git/1.0.0rc1/
>> https://pypi.org/project/apache-airflow-providers-github/2.12.0rc1/
>> https://pypi.org/project/apache-airflow-providers-google/22.6.0rc1/
>> https://pypi.org/project/apache-airflow-providers-grpc/3.10.0rc1/
>> https://pypi.org/project/apache-airflow-providers-hashicorp/4.8.2rc1/
>> https://pypi.org/project/apache-airflow-providers-http/6.2.0rc1/
>> https://pypi.org/project/apache-airflow-providers-imap/3.13.0rc1/
>> https://pypi.org/project/apache-airflow-providers-influxdb/2.12.0rc1/
>> https://pypi.org/project/apache-airflow-providers-keycloak/0.11.0rc1/
>>
>> https://pypi.org/project/apache-airflow-providers-microsoft-azure/15.2.0rc1/
>> https://pypi.org/project/apache-airflow-providers-microsoft-psrp/4.0.0rc1/
>>
>> https://pypi.org/project/apache-airflow-providers-microsoft-winrm/3.15.0rc1/
>> https://pypi.org/project/apache-airflow-providers-mongo/5.5.0rc1/
>> https://pypi.org/project/apache-airflow-providers-mysql/6.7.0rc1/
>> https://pypi.org/project/apache-airflow-providers-neo4j/3.13.0rc1/
>> https://pypi.org/project/apache-airflow-providers-openai/2.0.0rc1/
>> https://pypi.org/project/apache-airflow-providers-openlineage/2.20.2rc1/
>> https://pypi.org/project/apache-airflow-providers-opensearch/1.13.0rc1/
>> https://pypi.org/project/apache-airflow-providers-opsgenie/5.11.0rc1/
>> https://pypi.org/project/apache-airflow-providers-oracle/4.7.0rc1/
>> https://pypi.org/project/apache-airflow-providers-pagerduty/5.3.0rc1/
>> https://pypi.org/project/apache-airflow-providers-pinecone/2.5.0rc1/
>> https://pypi.org/project/apache-airflow-providers-postgres/7.1.0rc1/
>> https://pypi.org/project/apache-airflow-providers-presto/5.13.0rc1/
>> https://pypi.org/project/apache-airflow-providers-qdrant/1.6.0rc1/
>> https://pypi.org/project/apache-airflow-providers-redis/4.7.0rc1/
>> https://pypi.org/project/apache-airflow-providers-salesforce/5.15.0rc1/
>> https://pypi.org/project/apache-airflow-providers-samba/4.14.0rc1/
>> https://pypi.org/project/apache-airflow-providers-segment/3.10.0rc1/
>> https://pypi.org/project/apache-airflow-providers-sftp/6.1.0rc1/
>> https://pypi.org/project/apache-airflow-providers-slack/9.11.0rc1/
>> https://pypi.org/project/apache-airflow-providers-smtp/3.1.0rc1/
>> https://pypi.org/project/apache-airflow-providers-snowflake/6.18.0rc1/
>> https://pypi.org/project/apache-airflow-providers-ssh/6.1.0rc1/
>> https://pypi.org/project/apache-airflow-providers-standard/1.20.0rc1/
>> https://pypi.org/project/apache-airflow-providers-tableau/5.7.0rc1/
>> https://pypi.org/project/apache-airflow-providers-telegram/4.10.0rc1/
>> https://pypi.org/project/apache-airflow-providers-teradata/3.7.0rc1/
>> https://pypi.org/project/apache-airflow-providers-trino/6.7.0rc1/
>> https://pypi.org/project/apache-airflow-providers-weaviate/3.5.0rc1/
>> https://pypi.org/project/apache-airflow-providers-yandex/4.6.0rc1/
>>
>> Sincerely,
>> Shahar Epstein
>>
>

Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Shahar Epstein <sh...@apache.org>.
Hey everyone,

First - I'd like to thank everyone who has participated so far in testing
and voting, both on the devlist as well as the GitHub issue!
Second, due to some personal circumstances, I'll have to end the extended
vote earlier than planned, and start publishing the release around
2026-09-29 06:00 UTC.
Currently, only the edge provider is excluded from the release. If you find
justified reasons to exclude other providers, please cast your -1 vote in
the thread at earliest convenience.

Thank you for your understanding and cooperation!


Shahar

On Thu, Sep 24, 2026 at 3:30 PM Shahar Epstein <sh...@apache.org> wrote:

> Hey all,
>
> I have just cut the new wave Airflow Providers packages with release
> preparation date 2026-09-22. This email is calling a vote on the release,
> which will last for an extended period of 5 days - which means that it
> will end on 2026-09-29 12:00 UTC, with at least 3 binding +1 votes required
> for the release to pass.
>
> Consider this my (binding) +1.
> General highlights
>
>    - This wave includes many providers. Fun fact: there were so many that
>    I had to split the testing GitHub issue in two! This is mainly due to the
>    work on #35259, which adds connection ID templating across all providers.
>    - Work on #70296 is nearly complete, with a few exceptions (in
>    practice I resolved the issue). It moves template-field validation and
>    transformation out of __init__ so they run after template rendering,
>    preventing errors caused by processing unrendered values.
>    - We hope to graduate common.ai to 1.0.0 in the next RC, whether in a
>    wave or an ad hoc release. I'd like to ask the community's attention to
>    test this provider’s 0.10.0 RC extensively, as it includes many changes.
>    - To allow an appropriate time for testing all providers (in
>    particular: common.ai, fab, google, and amazon) - I extend the usualy
>    release vote period in extra two days than usual.
>
> Breaking changes and upgrade notes
>
>    - *edge3 4.3.2 → 5.0.0:* EdgeExecutor now counts queued workloads
>    against [core] parallelism. Review this setting if you rely on higher
>    concurrency (#72048).
>    - *git 0.5.0 → 1.0.0:* Token authentication now uses a credential
>    helper configured through GIT_CONFIG_COUNT and requires Git ≥ 2.31 on
>    Dag processors and workers (#64105).
>    - *microsoft.psrp 3.2.7 → 4.0.0:* PsrpOperator no longer defaults
>    task_id to the cmdlet; pass task_id explicitly (#73036).
>    - *openai 1.8.2 → 2.0.0:* create_embeddings now returns a list of
>    embedding vectors for list inputs, rather than only the first vector. This
>    also changes the XCom returned by OpenAIEmbeddingOperator for those
>    inputs (#71989).
>    - *common.ai <http://common.ai> 0.9.0 → 0.10.0:* PydanticAI vendor
>    connection types change from hyphens to underscores; SQLToolset now
>    rejects allowed_tables=None and allowed_tables=[] (omit the argument
>    to allow all tables); and execute_complete overrides on LLMOperator
>    and LLMBranchOperator must accept decision=None (#72853, #73381,
>    #73452, #73368).
>    - *Amazon:* Deferrable operators and sensors now pass their AWS
>    region, TLS verification, and botocore settings to triggers (#72171).
>    FTP/SFTP–S3 transfers now match filename prefixes rather than substrings
>    (#73269).
>
> Deprecations
>
>    - *Google Cloud Stackdriver:* Stackdriver components are renamed to
>    Cloud Monitoring and Cloud Logging (#73354, #73575). The Stackdriver*
>    operators, StackdriverHook, and Stackdriver links move to the new
>    CloudMonitoring* classes in the cloud_monitoring modules. The
>    Stackdriver task log handler becomes CloudLoggingTaskHandler in
>    cloud_logging_task_handler. The old names still work but emit
>    deprecation warnings; they are planned for removal after March 31, 2027.
>    - *Google Cloud Pub/Sub:* The default for return_immediately is
>    deprecated (#73504). PubSubPullOperator, PubSubPullSensor, and
>    PubsubPullTrigger now warn when return_immediately is not set. This
>    also applies to Google Pub/Sub asset watchers. The default will change from
>    True to False in the first Google provider major release after March
>    31, 2027. To preserve the current behavior, pass
>    return_immediately=True. The deferrable PubSubPullSensor now respects
>    this argument; previously, it dropped it, so the trigger always ran with
>    True.
>    - *Amazon QuickSight:* QuickSightHook.wait_for_state is deprecated in
>    favor of wait_for_ingestion, and the operator’s check_interval is
>    deprecated in favor of waiter_delay (#70218). No removal date has been
>    set.
>
>
>
> Airflow Providers are available at:
> https://dist.apache.org/repos/dist/dev/airflow/providers/2026-09-22
>
> *apache-airflow-providers-2026-09-22-source.tar.gz* is the full source
> tarball of airflow repo - snapshot taken at the moment of provider's
> release.
>
> *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the convenience python
> "sdist" distributions that we publish in PyPI
>
> *apache_airflow_providers_<PROVIDER>-*.whl are the convenience Python
> "wheel" distributions that we publish in PyPI.
>
> The test procedure for PMC members is described in
>
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-pmc-members
>
> The test procedure for and Contributors who would like to test this RC is
> described in:
>
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-contributors
>
>
> Public keys are available at:
> https://dist.apache.org/repos/dist/release/airflow/KEYS
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Only votes from PMC members are binding, but members of the community are
> encouraged to test the release and vote with "(non-binding)".
>
> Please note that the version number excludes the 'rcX' string.
> This will allow us to rename the artifact without modifying
> the artifact checksums when we actually release it.
>
> The status of testing the providers by the community is kept here:
> https://github.com/apache/airflow/issues/73658 - Part 1
> https://github.com/apache/airflow/issues/73658#issuecomment-5813334599 -
> Part 2
>
> The issue is also the easiest way to see important PRs included in the RC
> candidates.
> Detailed changelog for the providers will be published in the
> documentation after the
> RC candidates are released.
>
> You can find the RC packages in PyPI following these links:
>
> https://pypi.org/project/apache-airflow-providers-airbyte/6.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-alibaba/3.5.0rc1/
> https://pypi.org/project/apache-airflow-providers-amazon/9.37.0rc1/
> https://pypi.org/project/apache-airflow-providers-anthropic/1.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-beam/6.3.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-druid/4.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-flink/1.9.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.14.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-hive/9.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-kylin/3.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-livy/4.6.2rc1/
> https://pypi.org/project/apache-airflow-providers-apache-pig/4.9.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-apache-tinkerpop/1.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-apprise/2.4.0rc1/
> https://pypi.org/project/apache-airflow-providers-arangodb/2.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-asana/2.12.0rc1/
> https://pypi.org/project/apache-airflow-providers-atlassian-jira/3.4.0rc1/
> https://pypi.org/project/apache-airflow-providers-celery/3.24.1rc1/
> https://pypi.org/project/apache-airflow-providers-cloudant/4.3.6rc1/
>
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.23.0rc1/
> https://pypi.org/project/apache-airflow-providers-cohere/1.8.0rc1/
> https://pypi.org/project/apache-airflow-providers-common-ai/0.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-common-compat/1.20.0rc1/
> https://pypi.org/project/apache-airflow-providers-common-io/1.10.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-common-messaging/2.1.1rc1/
> https://pypi.org/project/apache-airflow-providers-common-sql/2.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-databricks/7.21.0rc1/
> https://pypi.org/project/apache-airflow-providers-datadog/3.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-dbt-cloud/4.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-dingding/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-docker/4.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-duckdb/0.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-edge3/5.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-exasol/4.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-fab/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-ftp/3.16.0rc1/
> https://pypi.org/project/apache-airflow-providers-git/1.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-github/2.12.0rc1/
> https://pypi.org/project/apache-airflow-providers-google/22.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-grpc/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-hashicorp/4.8.2rc1/
> https://pypi.org/project/apache-airflow-providers-http/6.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-imap/3.13.0rc1/
> https://pypi.org/project/apache-airflow-providers-influxdb/2.12.0rc1/
> https://pypi.org/project/apache-airflow-providers-keycloak/0.11.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-microsoft-azure/15.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-microsoft-psrp/4.0.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-microsoft-winrm/3.15.0rc1/
> https://pypi.org/project/apache-airflow-providers-mongo/5.5.0rc1/
> https://pypi.org/project/apache-airflow-providers-mysql/6.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-neo4j/3.13.0rc1/
> https://pypi.org/project/apache-airflow-providers-openai/2.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-openlineage/2.20.2rc1/
> https://pypi.org/project/apache-airflow-providers-opensearch/1.13.0rc1/
> https://pypi.org/project/apache-airflow-providers-opsgenie/5.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-oracle/4.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-pagerduty/5.3.0rc1/
> https://pypi.org/project/apache-airflow-providers-pinecone/2.5.0rc1/
> https://pypi.org/project/apache-airflow-providers-postgres/7.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-presto/5.13.0rc1/
> https://pypi.org/project/apache-airflow-providers-qdrant/1.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-redis/4.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-salesforce/5.15.0rc1/
> https://pypi.org/project/apache-airflow-providers-samba/4.14.0rc1/
> https://pypi.org/project/apache-airflow-providers-segment/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-sftp/6.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-slack/9.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-smtp/3.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-snowflake/6.18.0rc1/
> https://pypi.org/project/apache-airflow-providers-ssh/6.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-standard/1.20.0rc1/
> https://pypi.org/project/apache-airflow-providers-tableau/5.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-telegram/4.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-teradata/3.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-trino/6.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-weaviate/3.5.0rc1/
> https://pypi.org/project/apache-airflow-providers-yandex/4.6.0rc1/
>
> Sincerely,
> Shahar Epstein
>

Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Kaxil Naik <ka...@gmail.com>.
We have the ability to updating documentation after release too :) so we
don't need another rc for just doc changes -- fyi.

On Mon, 28 Sept 2026 at 14:53, Wei Lee <we...@apache.org> wrote:

> sure :)
>
> here it is https://github.com/apache/airflow/pull/73850
>
> On 2026/09/28 13:29:47 Shahar Epstein wrote:
> > It can, could you please raise a PR?
> >
> >
> > Shahar
> >
> >
> > On Mon, Sep 28, 2026, 16:20 Wei Lee <we...@apache.org> wrote:
> >
> > > The changelog in common.ai provider is technically right. (from commit
> > > history perspective)
> > >
> > > ```
> > > Add branch_descriptions to LLMBranchOperator so the model reads what
> each
> > > branch means (#73639)
> > > ```
> > >
> > > but it can be misleading as it's changed into branches later on (within
> > > 0.10.0rc1).
> > > Could we also change it before release?
> > >
> > > On 2026/09/28 10:40:34 Shahar Epstein wrote:
> > > > Thank you very much!
> > > > edge3 will be excluded from the current release (-1 binding).
> > > >
> > > >
> > > > Shahar
> > > >
> > > > On Mon, Sep 28, 2026 at 1:27 PM PoAn Yang <ya...@gmail.com>
> wrote:
> > > >
> > > > > Hi Shahar,
> > > > >
> > > > > Thanks for preparing this release!
> > > > >
> > > > > I found a regression in apache-airflow-providers-edge3 5.0.0rc1
> that
> > > comes
> > > > > from my own PR #72048 [1]. When the scheduler restarts while Edge
> task
> > > > > instances from the previous scheduler are still queued or running,
> the
> > > new
> > > > > scheduler crashes on startup with DetachedInstanceError. It keeps
> > > crashing
> > > > > the same way on every restart for as long as those task instances
> stay
> > > > > queued or running. I reproduced it with the RC from PyPI on Airflow
> > > 3.3.2.
> > > > > The edge3 4.3.2 does not have the problem. I also tried the upgrade
> > > path:
> > > > > after a scheduler running edge3 4.3.2 queues some Edge tasks and
> > > stops, the
> > > > > first scheduler start after upgrading to 5.0.0rc1 crashes the same
> way.
> > > > >
> > > > > Could we exclude edge3? The fix is in [2]. Once that PR is merged,
> > > edge3
> > > > > could go out in an rc2.
> > > > >
> > > > > +1 (non-binding) for amazon, apache.beam and google
> > > > > -1 (non-binding) for edge3 because of this regression
> > > > >
> > > > > [1] https://github.com/apache/airflow/pull/72048
> > > > > [2] https://github.com/apache/airflow/pull/73832
> > > > >
> > > > > Thanks,
> > > > > PoAn
> > > > >
> > > > >
> > > > > > On Sep 27, 2026, at 4:00 PM, Sameer Mesiah <smesiah971@gmail.com
> >
> > > wrote:
> > > > > >
> > > > > > +1 (non-binding)
> > > > > >
> > > > > > I can verify that my changes for the Amazon and Snowflake
> providers
> > > for
> > > > > > this release wave are working as expected.
> > > > > >
> > > > > > On Fri, 25 Sep 2026 at 09:50, Wei Lee <we...@apache.org> wrote:
> > > > > >
> > > > > >> +1 (binding), checked:
> > > > > >>
> > > > > >> - SVN
> > > > > >> - in Docker installation
> > > > > >> - Reproducible package builds
> > > > > >> - Licence
> > > > > >> - Signature
> > > > > >> - Checksums
> > > > > >>
> > > > > >> Thanks!
> > > > > >>
> > > > > >> Best regards,
> > > > > >> Wei Lee
> > > > > >>
> > > > > >> On 2026/09/25 08:22:48 Pankaj Koti via dev wrote:
> > > > > >>> +1 non-binding
> > > > > >>>
> > > > > >>> Tested that my PRs are included in the RC and working as
> expected,
> > > > > thanks
> > > > > >>> for cutting the release!
> > > > > >>>
> > > > > >>> On Fri, Sep 25, 2026 at 3:32 AM Jarek Potiuk <jarek@potiuk.com
> >
> > > wrote:
> > > > > >>>
> > > > > >>>> +1 (binding)
> > > > > >>>>
> > > > > >>>> Checked:
> > > > > >>>>
> > > > > >>>> * SVN: all expected files present (check-release-files), and
> all
> > > 78 RC
> > > > > >>>>  providers install at their RC versions (Dockerfile.pmc)
> > > > > >>>> * Signatures: all 157 good (Shahar's key from KEYS)
> > > > > >>>> * Checksums: all 157 SHA512 good
> > > > > >>>> * Licences: Apache RAT 0.18 - 0 unapproved, 0 unknown
> > > > > >>>> * Reproducible builds: the source tarball and all 156
> packages are
> > > > > >>>>  byte-identical when rebuilt from the providers/2026-09-22 tag
> > > with
> > > > > >>>>  flit 4.0.2
> > > > > >>>>
> > > > > >>>> One note on reproducibility, not a blocker: the wheels were
> built
> > > with
> > > > > >>>> flit 4.0.2, but dev/breeze/uv.lock at the tag locks flit
> 4.1.0.
> > > Since
> > > > > >>>> flit builds without isolation, rebuilding with the locked
> Breeze
> > > (as
> > > > > >>>> the docs say) gives 75 wheels that differ only in the
> "Generator:"
> > > > > >>>> line of their WHEEL file (and its hash in RECORD) - the
> packaged
> > > files
> > > > > >>>> are identical. I opened a PR explaining how to rebuild with
> the
> > > > > >>>> release manager's flit version:
> > > > > >>>> https://github.com/apache/airflow/pull/73699
> > > > > >>>>
> > > > > >>>> I also tested all my changes in this wave with all 78 RC
> providers
> > > > > >>>> installed from the PyPI wheels in Breeze (Airflow 3.3.2):
> > > > > >>>>
> > > > > >>>> * #72162 (amazon, google, microsoft.azure) - remote log
> uploads
> > > > > outside
> > > > > >>>>  base_log_folder are skipped, uploads inside still work
> > > > > >>>> * #72166 (google) - Drive q= values are escaped
> > > > > >>>> * #73413 (common.sql) - DataFusion error message shows the
> storage
> > > > > type
> > > > > >>>> * #72627 (edge3) - docs only, present in the release
> > > > > >>>> * #72174 (snowflake) and #72176 (teradata) - in the wave,
> though
> > > not
> > > > > >>>>  listed in the testing issue - both work as expected
> > > > > >>>>
> > > > > >>>> Improvement to the verification process:
> > > > > >>>>
> > > > > >>>> I tested all my changes with an agent using Apache Magpie's
> > > > > >>>> release-management
> > > > > >>>> "verify-rc" skill and a new Airflow override that adds an
> optional
> > > > > >> "test
> > > > > >>>> your own changes" step. The agent found my entries in the
> testing
> > > > > issue
> > > > > >>>> (and the two changes missing from it), verified each change
> is in
> > > the
> > > > > >>>> RC tags, changelogs and wheels, downloaded the whole wave and
> > > wrote a
> > > > > >>>> Dag exercising every change - I only had to start Breeze and
> > > trigger
> > > > > >> it.
> > > > > >>>> It also ran the regular checks above and tracked down the flit
> > > > > >>>> difference.
> > > > > >>>>
> > > > > >>>> That was a very good experience - I highly recommend trying
> it:
> > > > > >>>> https://github.com/apache/airflow/pull/73697
> > > > > >>>>
> > > > > >>>> J.
> > > > > >>>>
> > > > > >>>>
> > > ---------------------------------------------------------------------
> > > > > >>>> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > > > >>>> For additional commands, e-mail: dev-help@airflow.apache.org
> > > > > >>>>
> > > > > >>>>
> > > > > >>>
> > > > > >>
> > > > > >>
> > > ---------------------------------------------------------------------
> > > > > >> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > > > >> For additional commands, e-mail: dev-help@airflow.apache.org
> > > > > >>
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > For additional commands, e-mail: dev-help@airflow.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> For additional commands, e-mail: dev-help@airflow.apache.org
>
>

Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Wei Lee <we...@apache.org>.
sure :)

here it is https://github.com/apache/airflow/pull/73850

On 2026/09/28 13:29:47 Shahar Epstein wrote:
> It can, could you please raise a PR?
> 
> 
> Shahar
> 
> 
> On Mon, Sep 28, 2026, 16:20 Wei Lee <we...@apache.org> wrote:
> 
> > The changelog in common.ai provider is technically right. (from commit
> > history perspective)
> >
> > ```
> > Add branch_descriptions to LLMBranchOperator so the model reads what each
> > branch means (#73639)
> > ```
> >
> > but it can be misleading as it's changed into branches later on (within
> > 0.10.0rc1).
> > Could we also change it before release?
> >
> > On 2026/09/28 10:40:34 Shahar Epstein wrote:
> > > Thank you very much!
> > > edge3 will be excluded from the current release (-1 binding).
> > >
> > >
> > > Shahar
> > >
> > > On Mon, Sep 28, 2026 at 1:27 PM PoAn Yang <ya...@gmail.com> wrote:
> > >
> > > > Hi Shahar,
> > > >
> > > > Thanks for preparing this release!
> > > >
> > > > I found a regression in apache-airflow-providers-edge3 5.0.0rc1 that
> > comes
> > > > from my own PR #72048 [1]. When the scheduler restarts while Edge task
> > > > instances from the previous scheduler are still queued or running, the
> > new
> > > > scheduler crashes on startup with DetachedInstanceError. It keeps
> > crashing
> > > > the same way on every restart for as long as those task instances stay
> > > > queued or running. I reproduced it with the RC from PyPI on Airflow
> > 3.3.2.
> > > > The edge3 4.3.2 does not have the problem. I also tried the upgrade
> > path:
> > > > after a scheduler running edge3 4.3.2 queues some Edge tasks and
> > stops, the
> > > > first scheduler start after upgrading to 5.0.0rc1 crashes the same way.
> > > >
> > > > Could we exclude edge3? The fix is in [2]. Once that PR is merged,
> > edge3
> > > > could go out in an rc2.
> > > >
> > > > +1 (non-binding) for amazon, apache.beam and google
> > > > -1 (non-binding) for edge3 because of this regression
> > > >
> > > > [1] https://github.com/apache/airflow/pull/72048
> > > > [2] https://github.com/apache/airflow/pull/73832
> > > >
> > > > Thanks,
> > > > PoAn
> > > >
> > > >
> > > > > On Sep 27, 2026, at 4:00 PM, Sameer Mesiah <sm...@gmail.com>
> > wrote:
> > > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > I can verify that my changes for the Amazon and Snowflake providers
> > for
> > > > > this release wave are working as expected.
> > > > >
> > > > > On Fri, 25 Sep 2026 at 09:50, Wei Lee <we...@apache.org> wrote:
> > > > >
> > > > >> +1 (binding), checked:
> > > > >>
> > > > >> - SVN
> > > > >> - in Docker installation
> > > > >> - Reproducible package builds
> > > > >> - Licence
> > > > >> - Signature
> > > > >> - Checksums
> > > > >>
> > > > >> Thanks!
> > > > >>
> > > > >> Best regards,
> > > > >> Wei Lee
> > > > >>
> > > > >> On 2026/09/25 08:22:48 Pankaj Koti via dev wrote:
> > > > >>> +1 non-binding
> > > > >>>
> > > > >>> Tested that my PRs are included in the RC and working as expected,
> > > > thanks
> > > > >>> for cutting the release!
> > > > >>>
> > > > >>> On Fri, Sep 25, 2026 at 3:32 AM Jarek Potiuk <ja...@potiuk.com>
> > wrote:
> > > > >>>
> > > > >>>> +1 (binding)
> > > > >>>>
> > > > >>>> Checked:
> > > > >>>>
> > > > >>>> * SVN: all expected files present (check-release-files), and all
> > 78 RC
> > > > >>>>  providers install at their RC versions (Dockerfile.pmc)
> > > > >>>> * Signatures: all 157 good (Shahar's key from KEYS)
> > > > >>>> * Checksums: all 157 SHA512 good
> > > > >>>> * Licences: Apache RAT 0.18 - 0 unapproved, 0 unknown
> > > > >>>> * Reproducible builds: the source tarball and all 156 packages are
> > > > >>>>  byte-identical when rebuilt from the providers/2026-09-22 tag
> > with
> > > > >>>>  flit 4.0.2
> > > > >>>>
> > > > >>>> One note on reproducibility, not a blocker: the wheels were built
> > with
> > > > >>>> flit 4.0.2, but dev/breeze/uv.lock at the tag locks flit 4.1.0.
> > Since
> > > > >>>> flit builds without isolation, rebuilding with the locked Breeze
> > (as
> > > > >>>> the docs say) gives 75 wheels that differ only in the "Generator:"
> > > > >>>> line of their WHEEL file (and its hash in RECORD) - the packaged
> > files
> > > > >>>> are identical. I opened a PR explaining how to rebuild with the
> > > > >>>> release manager's flit version:
> > > > >>>> https://github.com/apache/airflow/pull/73699
> > > > >>>>
> > > > >>>> I also tested all my changes in this wave with all 78 RC providers
> > > > >>>> installed from the PyPI wheels in Breeze (Airflow 3.3.2):
> > > > >>>>
> > > > >>>> * #72162 (amazon, google, microsoft.azure) - remote log uploads
> > > > outside
> > > > >>>>  base_log_folder are skipped, uploads inside still work
> > > > >>>> * #72166 (google) - Drive q= values are escaped
> > > > >>>> * #73413 (common.sql) - DataFusion error message shows the storage
> > > > type
> > > > >>>> * #72627 (edge3) - docs only, present in the release
> > > > >>>> * #72174 (snowflake) and #72176 (teradata) - in the wave, though
> > not
> > > > >>>>  listed in the testing issue - both work as expected
> > > > >>>>
> > > > >>>> Improvement to the verification process:
> > > > >>>>
> > > > >>>> I tested all my changes with an agent using Apache Magpie's
> > > > >>>> release-management
> > > > >>>> "verify-rc" skill and a new Airflow override that adds an optional
> > > > >> "test
> > > > >>>> your own changes" step. The agent found my entries in the testing
> > > > issue
> > > > >>>> (and the two changes missing from it), verified each change is in
> > the
> > > > >>>> RC tags, changelogs and wheels, downloaded the whole wave and
> > wrote a
> > > > >>>> Dag exercising every change - I only had to start Breeze and
> > trigger
> > > > >> it.
> > > > >>>> It also ran the regular checks above and tracked down the flit
> > > > >>>> difference.
> > > > >>>>
> > > > >>>> That was a very good experience - I highly recommend trying it:
> > > > >>>> https://github.com/apache/airflow/pull/73697
> > > > >>>>
> > > > >>>> J.
> > > > >>>>
> > > > >>>>
> > ---------------------------------------------------------------------
> > > > >>>> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > > >>>> For additional commands, e-mail: dev-help@airflow.apache.org
> > > > >>>>
> > > > >>>>
> > > > >>>
> > > > >>
> > > > >>
> > ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > > >> For additional commands, e-mail: dev-help@airflow.apache.org
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > For additional commands, e-mail: dev-help@airflow.apache.org
> >
> >
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
For additional commands, e-mail: dev-help@airflow.apache.org


Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Shahar Epstein <sh...@apache.org>.
It can, could you please raise a PR?


Shahar


On Mon, Sep 28, 2026, 16:20 Wei Lee <we...@apache.org> wrote:

> The changelog in common.ai provider is technically right. (from commit
> history perspective)
>
> ```
> Add branch_descriptions to LLMBranchOperator so the model reads what each
> branch means (#73639)
> ```
>
> but it can be misleading as it's changed into branches later on (within
> 0.10.0rc1).
> Could we also change it before release?
>
> On 2026/09/28 10:40:34 Shahar Epstein wrote:
> > Thank you very much!
> > edge3 will be excluded from the current release (-1 binding).
> >
> >
> > Shahar
> >
> > On Mon, Sep 28, 2026 at 1:27 PM PoAn Yang <ya...@gmail.com> wrote:
> >
> > > Hi Shahar,
> > >
> > > Thanks for preparing this release!
> > >
> > > I found a regression in apache-airflow-providers-edge3 5.0.0rc1 that
> comes
> > > from my own PR #72048 [1]. When the scheduler restarts while Edge task
> > > instances from the previous scheduler are still queued or running, the
> new
> > > scheduler crashes on startup with DetachedInstanceError. It keeps
> crashing
> > > the same way on every restart for as long as those task instances stay
> > > queued or running. I reproduced it with the RC from PyPI on Airflow
> 3.3.2.
> > > The edge3 4.3.2 does not have the problem. I also tried the upgrade
> path:
> > > after a scheduler running edge3 4.3.2 queues some Edge tasks and
> stops, the
> > > first scheduler start after upgrading to 5.0.0rc1 crashes the same way.
> > >
> > > Could we exclude edge3? The fix is in [2]. Once that PR is merged,
> edge3
> > > could go out in an rc2.
> > >
> > > +1 (non-binding) for amazon, apache.beam and google
> > > -1 (non-binding) for edge3 because of this regression
> > >
> > > [1] https://github.com/apache/airflow/pull/72048
> > > [2] https://github.com/apache/airflow/pull/73832
> > >
> > > Thanks,
> > > PoAn
> > >
> > >
> > > > On Sep 27, 2026, at 4:00 PM, Sameer Mesiah <sm...@gmail.com>
> wrote:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > I can verify that my changes for the Amazon and Snowflake providers
> for
> > > > this release wave are working as expected.
> > > >
> > > > On Fri, 25 Sep 2026 at 09:50, Wei Lee <we...@apache.org> wrote:
> > > >
> > > >> +1 (binding), checked:
> > > >>
> > > >> - SVN
> > > >> - in Docker installation
> > > >> - Reproducible package builds
> > > >> - Licence
> > > >> - Signature
> > > >> - Checksums
> > > >>
> > > >> Thanks!
> > > >>
> > > >> Best regards,
> > > >> Wei Lee
> > > >>
> > > >> On 2026/09/25 08:22:48 Pankaj Koti via dev wrote:
> > > >>> +1 non-binding
> > > >>>
> > > >>> Tested that my PRs are included in the RC and working as expected,
> > > thanks
> > > >>> for cutting the release!
> > > >>>
> > > >>> On Fri, Sep 25, 2026 at 3:32 AM Jarek Potiuk <ja...@potiuk.com>
> wrote:
> > > >>>
> > > >>>> +1 (binding)
> > > >>>>
> > > >>>> Checked:
> > > >>>>
> > > >>>> * SVN: all expected files present (check-release-files), and all
> 78 RC
> > > >>>>  providers install at their RC versions (Dockerfile.pmc)
> > > >>>> * Signatures: all 157 good (Shahar's key from KEYS)
> > > >>>> * Checksums: all 157 SHA512 good
> > > >>>> * Licences: Apache RAT 0.18 - 0 unapproved, 0 unknown
> > > >>>> * Reproducible builds: the source tarball and all 156 packages are
> > > >>>>  byte-identical when rebuilt from the providers/2026-09-22 tag
> with
> > > >>>>  flit 4.0.2
> > > >>>>
> > > >>>> One note on reproducibility, not a blocker: the wheels were built
> with
> > > >>>> flit 4.0.2, but dev/breeze/uv.lock at the tag locks flit 4.1.0.
> Since
> > > >>>> flit builds without isolation, rebuilding with the locked Breeze
> (as
> > > >>>> the docs say) gives 75 wheels that differ only in the "Generator:"
> > > >>>> line of their WHEEL file (and its hash in RECORD) - the packaged
> files
> > > >>>> are identical. I opened a PR explaining how to rebuild with the
> > > >>>> release manager's flit version:
> > > >>>> https://github.com/apache/airflow/pull/73699
> > > >>>>
> > > >>>> I also tested all my changes in this wave with all 78 RC providers
> > > >>>> installed from the PyPI wheels in Breeze (Airflow 3.3.2):
> > > >>>>
> > > >>>> * #72162 (amazon, google, microsoft.azure) - remote log uploads
> > > outside
> > > >>>>  base_log_folder are skipped, uploads inside still work
> > > >>>> * #72166 (google) - Drive q= values are escaped
> > > >>>> * #73413 (common.sql) - DataFusion error message shows the storage
> > > type
> > > >>>> * #72627 (edge3) - docs only, present in the release
> > > >>>> * #72174 (snowflake) and #72176 (teradata) - in the wave, though
> not
> > > >>>>  listed in the testing issue - both work as expected
> > > >>>>
> > > >>>> Improvement to the verification process:
> > > >>>>
> > > >>>> I tested all my changes with an agent using Apache Magpie's
> > > >>>> release-management
> > > >>>> "verify-rc" skill and a new Airflow override that adds an optional
> > > >> "test
> > > >>>> your own changes" step. The agent found my entries in the testing
> > > issue
> > > >>>> (and the two changes missing from it), verified each change is in
> the
> > > >>>> RC tags, changelogs and wheels, downloaded the whole wave and
> wrote a
> > > >>>> Dag exercising every change - I only had to start Breeze and
> trigger
> > > >> it.
> > > >>>> It also ran the regular checks above and tracked down the flit
> > > >>>> difference.
> > > >>>>
> > > >>>> That was a very good experience - I highly recommend trying it:
> > > >>>> https://github.com/apache/airflow/pull/73697
> > > >>>>
> > > >>>> J.
> > > >>>>
> > > >>>>
> ---------------------------------------------------------------------
> > > >>>> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > >>>> For additional commands, e-mail: dev-help@airflow.apache.org
> > > >>>>
> > > >>>>
> > > >>>
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > >> For additional commands, e-mail: dev-help@airflow.apache.org
> > > >>
> > > >>
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> For additional commands, e-mail: dev-help@airflow.apache.org
>
>

Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Wei Lee <we...@apache.org>.
The changelog in common.ai provider is technically right. (from commit history perspective)

```
Add branch_descriptions to LLMBranchOperator so the model reads what each branch means (#73639)
```

but it can be misleading as it's changed into branches later on (within 0.10.0rc1).
Could we also change it before release?

On 2026/09/28 10:40:34 Shahar Epstein wrote:
> Thank you very much!
> edge3 will be excluded from the current release (-1 binding).
> 
> 
> Shahar
> 
> On Mon, Sep 28, 2026 at 1:27 PM PoAn Yang <ya...@gmail.com> wrote:
> 
> > Hi Shahar,
> >
> > Thanks for preparing this release!
> >
> > I found a regression in apache-airflow-providers-edge3 5.0.0rc1 that comes
> > from my own PR #72048 [1]. When the scheduler restarts while Edge task
> > instances from the previous scheduler are still queued or running, the new
> > scheduler crashes on startup with DetachedInstanceError. It keeps crashing
> > the same way on every restart for as long as those task instances stay
> > queued or running. I reproduced it with the RC from PyPI on Airflow 3.3.2.
> > The edge3 4.3.2 does not have the problem. I also tried the upgrade path:
> > after a scheduler running edge3 4.3.2 queues some Edge tasks and stops, the
> > first scheduler start after upgrading to 5.0.0rc1 crashes the same way.
> >
> > Could we exclude edge3? The fix is in [2]. Once that PR is merged, edge3
> > could go out in an rc2.
> >
> > +1 (non-binding) for amazon, apache.beam and google
> > -1 (non-binding) for edge3 because of this regression
> >
> > [1] https://github.com/apache/airflow/pull/72048
> > [2] https://github.com/apache/airflow/pull/73832
> >
> > Thanks,
> > PoAn
> >
> >
> > > On Sep 27, 2026, at 4:00 PM, Sameer Mesiah <sm...@gmail.com> wrote:
> > >
> > > +1 (non-binding)
> > >
> > > I can verify that my changes for the Amazon and Snowflake providers for
> > > this release wave are working as expected.
> > >
> > > On Fri, 25 Sep 2026 at 09:50, Wei Lee <we...@apache.org> wrote:
> > >
> > >> +1 (binding), checked:
> > >>
> > >> - SVN
> > >> - in Docker installation
> > >> - Reproducible package builds
> > >> - Licence
> > >> - Signature
> > >> - Checksums
> > >>
> > >> Thanks!
> > >>
> > >> Best regards,
> > >> Wei Lee
> > >>
> > >> On 2026/09/25 08:22:48 Pankaj Koti via dev wrote:
> > >>> +1 non-binding
> > >>>
> > >>> Tested that my PRs are included in the RC and working as expected,
> > thanks
> > >>> for cutting the release!
> > >>>
> > >>> On Fri, Sep 25, 2026 at 3:32 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> > >>>
> > >>>> +1 (binding)
> > >>>>
> > >>>> Checked:
> > >>>>
> > >>>> * SVN: all expected files present (check-release-files), and all 78 RC
> > >>>>  providers install at their RC versions (Dockerfile.pmc)
> > >>>> * Signatures: all 157 good (Shahar's key from KEYS)
> > >>>> * Checksums: all 157 SHA512 good
> > >>>> * Licences: Apache RAT 0.18 - 0 unapproved, 0 unknown
> > >>>> * Reproducible builds: the source tarball and all 156 packages are
> > >>>>  byte-identical when rebuilt from the providers/2026-09-22 tag with
> > >>>>  flit 4.0.2
> > >>>>
> > >>>> One note on reproducibility, not a blocker: the wheels were built with
> > >>>> flit 4.0.2, but dev/breeze/uv.lock at the tag locks flit 4.1.0. Since
> > >>>> flit builds without isolation, rebuilding with the locked Breeze (as
> > >>>> the docs say) gives 75 wheels that differ only in the "Generator:"
> > >>>> line of their WHEEL file (and its hash in RECORD) - the packaged files
> > >>>> are identical. I opened a PR explaining how to rebuild with the
> > >>>> release manager's flit version:
> > >>>> https://github.com/apache/airflow/pull/73699
> > >>>>
> > >>>> I also tested all my changes in this wave with all 78 RC providers
> > >>>> installed from the PyPI wheels in Breeze (Airflow 3.3.2):
> > >>>>
> > >>>> * #72162 (amazon, google, microsoft.azure) - remote log uploads
> > outside
> > >>>>  base_log_folder are skipped, uploads inside still work
> > >>>> * #72166 (google) - Drive q= values are escaped
> > >>>> * #73413 (common.sql) - DataFusion error message shows the storage
> > type
> > >>>> * #72627 (edge3) - docs only, present in the release
> > >>>> * #72174 (snowflake) and #72176 (teradata) - in the wave, though not
> > >>>>  listed in the testing issue - both work as expected
> > >>>>
> > >>>> Improvement to the verification process:
> > >>>>
> > >>>> I tested all my changes with an agent using Apache Magpie's
> > >>>> release-management
> > >>>> "verify-rc" skill and a new Airflow override that adds an optional
> > >> "test
> > >>>> your own changes" step. The agent found my entries in the testing
> > issue
> > >>>> (and the two changes missing from it), verified each change is in the
> > >>>> RC tags, changelogs and wheels, downloaded the whole wave and wrote a
> > >>>> Dag exercising every change - I only had to start Breeze and trigger
> > >> it.
> > >>>> It also ran the regular checks above and tracked down the flit
> > >>>> difference.
> > >>>>
> > >>>> That was a very good experience - I highly recommend trying it:
> > >>>> https://github.com/apache/airflow/pull/73697
> > >>>>
> > >>>> J.
> > >>>>
> > >>>> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > >>>> For additional commands, e-mail: dev-help@airflow.apache.org
> > >>>>
> > >>>>
> > >>>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > >> For additional commands, e-mail: dev-help@airflow.apache.org
> > >>
> > >>
> >
> >
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
For additional commands, e-mail: dev-help@airflow.apache.org


Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Shahar Epstein <sh...@apache.org>.
Thank you very much!
edge3 will be excluded from the current release (-1 binding).


Shahar

On Mon, Sep 28, 2026 at 1:27 PM PoAn Yang <ya...@gmail.com> wrote:

> Hi Shahar,
>
> Thanks for preparing this release!
>
> I found a regression in apache-airflow-providers-edge3 5.0.0rc1 that comes
> from my own PR #72048 [1]. When the scheduler restarts while Edge task
> instances from the previous scheduler are still queued or running, the new
> scheduler crashes on startup with DetachedInstanceError. It keeps crashing
> the same way on every restart for as long as those task instances stay
> queued or running. I reproduced it with the RC from PyPI on Airflow 3.3.2.
> The edge3 4.3.2 does not have the problem. I also tried the upgrade path:
> after a scheduler running edge3 4.3.2 queues some Edge tasks and stops, the
> first scheduler start after upgrading to 5.0.0rc1 crashes the same way.
>
> Could we exclude edge3? The fix is in [2]. Once that PR is merged, edge3
> could go out in an rc2.
>
> +1 (non-binding) for amazon, apache.beam and google
> -1 (non-binding) for edge3 because of this regression
>
> [1] https://github.com/apache/airflow/pull/72048
> [2] https://github.com/apache/airflow/pull/73832
>
> Thanks,
> PoAn
>
>
> > On Sep 27, 2026, at 4:00 PM, Sameer Mesiah <sm...@gmail.com> wrote:
> >
> > +1 (non-binding)
> >
> > I can verify that my changes for the Amazon and Snowflake providers for
> > this release wave are working as expected.
> >
> > On Fri, 25 Sep 2026 at 09:50, Wei Lee <we...@apache.org> wrote:
> >
> >> +1 (binding), checked:
> >>
> >> - SVN
> >> - in Docker installation
> >> - Reproducible package builds
> >> - Licence
> >> - Signature
> >> - Checksums
> >>
> >> Thanks!
> >>
> >> Best regards,
> >> Wei Lee
> >>
> >> On 2026/09/25 08:22:48 Pankaj Koti via dev wrote:
> >>> +1 non-binding
> >>>
> >>> Tested that my PRs are included in the RC and working as expected,
> thanks
> >>> for cutting the release!
> >>>
> >>> On Fri, Sep 25, 2026 at 3:32 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> >>>
> >>>> +1 (binding)
> >>>>
> >>>> Checked:
> >>>>
> >>>> * SVN: all expected files present (check-release-files), and all 78 RC
> >>>>  providers install at their RC versions (Dockerfile.pmc)
> >>>> * Signatures: all 157 good (Shahar's key from KEYS)
> >>>> * Checksums: all 157 SHA512 good
> >>>> * Licences: Apache RAT 0.18 - 0 unapproved, 0 unknown
> >>>> * Reproducible builds: the source tarball and all 156 packages are
> >>>>  byte-identical when rebuilt from the providers/2026-09-22 tag with
> >>>>  flit 4.0.2
> >>>>
> >>>> One note on reproducibility, not a blocker: the wheels were built with
> >>>> flit 4.0.2, but dev/breeze/uv.lock at the tag locks flit 4.1.0. Since
> >>>> flit builds without isolation, rebuilding with the locked Breeze (as
> >>>> the docs say) gives 75 wheels that differ only in the "Generator:"
> >>>> line of their WHEEL file (and its hash in RECORD) - the packaged files
> >>>> are identical. I opened a PR explaining how to rebuild with the
> >>>> release manager's flit version:
> >>>> https://github.com/apache/airflow/pull/73699
> >>>>
> >>>> I also tested all my changes in this wave with all 78 RC providers
> >>>> installed from the PyPI wheels in Breeze (Airflow 3.3.2):
> >>>>
> >>>> * #72162 (amazon, google, microsoft.azure) - remote log uploads
> outside
> >>>>  base_log_folder are skipped, uploads inside still work
> >>>> * #72166 (google) - Drive q= values are escaped
> >>>> * #73413 (common.sql) - DataFusion error message shows the storage
> type
> >>>> * #72627 (edge3) - docs only, present in the release
> >>>> * #72174 (snowflake) and #72176 (teradata) - in the wave, though not
> >>>>  listed in the testing issue - both work as expected
> >>>>
> >>>> Improvement to the verification process:
> >>>>
> >>>> I tested all my changes with an agent using Apache Magpie's
> >>>> release-management
> >>>> "verify-rc" skill and a new Airflow override that adds an optional
> >> "test
> >>>> your own changes" step. The agent found my entries in the testing
> issue
> >>>> (and the two changes missing from it), verified each change is in the
> >>>> RC tags, changelogs and wheels, downloaded the whole wave and wrote a
> >>>> Dag exercising every change - I only had to start Breeze and trigger
> >> it.
> >>>> It also ran the regular checks above and tracked down the flit
> >>>> difference.
> >>>>
> >>>> That was a very good experience - I highly recommend trying it:
> >>>> https://github.com/apache/airflow/pull/73697
> >>>>
> >>>> J.
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> >>>> For additional commands, e-mail: dev-help@airflow.apache.org
> >>>>
> >>>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> >> For additional commands, e-mail: dev-help@airflow.apache.org
> >>
> >>
>
>

Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by PoAn Yang <ya...@gmail.com>.
Hi Shahar,

Thanks for preparing this release!

I found a regression in apache-airflow-providers-edge3 5.0.0rc1 that comes from my own PR #72048 [1]. When the scheduler restarts while Edge task instances from the previous scheduler are still queued or running, the new scheduler crashes on startup with DetachedInstanceError. It keeps crashing the same way on every restart for as long as those task instances stay queued or running. I reproduced it with the RC from PyPI on Airflow 3.3.2. The edge3 4.3.2 does not have the problem. I also tried the upgrade path: after a scheduler running edge3 4.3.2 queues some Edge tasks and stops, the first scheduler start after upgrading to 5.0.0rc1 crashes the same way.

Could we exclude edge3? The fix is in [2]. Once that PR is merged, edge3 could go out in an rc2.

+1 (non-binding) for amazon, apache.beam and google
-1 (non-binding) for edge3 because of this regression

[1] https://github.com/apache/airflow/pull/72048
[2] https://github.com/apache/airflow/pull/73832

Thanks,
PoAn


> On Sep 27, 2026, at 4:00 PM, Sameer Mesiah <sm...@gmail.com> wrote:
> 
> +1 (non-binding)
> 
> I can verify that my changes for the Amazon and Snowflake providers for
> this release wave are working as expected.
> 
> On Fri, 25 Sep 2026 at 09:50, Wei Lee <we...@apache.org> wrote:
> 
>> +1 (binding), checked:
>> 
>> - SVN
>> - in Docker installation
>> - Reproducible package builds
>> - Licence
>> - Signature
>> - Checksums
>> 
>> Thanks!
>> 
>> Best regards,
>> Wei Lee
>> 
>> On 2026/09/25 08:22:48 Pankaj Koti via dev wrote:
>>> +1 non-binding
>>> 
>>> Tested that my PRs are included in the RC and working as expected, thanks
>>> for cutting the release!
>>> 
>>> On Fri, Sep 25, 2026 at 3:32 AM Jarek Potiuk <ja...@potiuk.com> wrote:
>>> 
>>>> +1 (binding)
>>>> 
>>>> Checked:
>>>> 
>>>> * SVN: all expected files present (check-release-files), and all 78 RC
>>>>  providers install at their RC versions (Dockerfile.pmc)
>>>> * Signatures: all 157 good (Shahar's key from KEYS)
>>>> * Checksums: all 157 SHA512 good
>>>> * Licences: Apache RAT 0.18 - 0 unapproved, 0 unknown
>>>> * Reproducible builds: the source tarball and all 156 packages are
>>>>  byte-identical when rebuilt from the providers/2026-09-22 tag with
>>>>  flit 4.0.2
>>>> 
>>>> One note on reproducibility, not a blocker: the wheels were built with
>>>> flit 4.0.2, but dev/breeze/uv.lock at the tag locks flit 4.1.0. Since
>>>> flit builds without isolation, rebuilding with the locked Breeze (as
>>>> the docs say) gives 75 wheels that differ only in the "Generator:"
>>>> line of their WHEEL file (and its hash in RECORD) - the packaged files
>>>> are identical. I opened a PR explaining how to rebuild with the
>>>> release manager's flit version:
>>>> https://github.com/apache/airflow/pull/73699
>>>> 
>>>> I also tested all my changes in this wave with all 78 RC providers
>>>> installed from the PyPI wheels in Breeze (Airflow 3.3.2):
>>>> 
>>>> * #72162 (amazon, google, microsoft.azure) - remote log uploads outside
>>>>  base_log_folder are skipped, uploads inside still work
>>>> * #72166 (google) - Drive q= values are escaped
>>>> * #73413 (common.sql) - DataFusion error message shows the storage type
>>>> * #72627 (edge3) - docs only, present in the release
>>>> * #72174 (snowflake) and #72176 (teradata) - in the wave, though not
>>>>  listed in the testing issue - both work as expected
>>>> 
>>>> Improvement to the verification process:
>>>> 
>>>> I tested all my changes with an agent using Apache Magpie's
>>>> release-management
>>>> "verify-rc" skill and a new Airflow override that adds an optional
>> "test
>>>> your own changes" step. The agent found my entries in the testing issue
>>>> (and the two changes missing from it), verified each change is in the
>>>> RC tags, changelogs and wheels, downloaded the whole wave and wrote a
>>>> Dag exercising every change - I only had to start Breeze and trigger
>> it.
>>>> It also ran the regular checks above and tracked down the flit
>>>> difference.
>>>> 
>>>> That was a very good experience - I highly recommend trying it:
>>>> https://github.com/apache/airflow/pull/73697
>>>> 
>>>> J.
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
>>>> For additional commands, e-mail: dev-help@airflow.apache.org
>>>> 
>>>> 
>>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
>> For additional commands, e-mail: dev-help@airflow.apache.org
>> 
>> 


Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Sameer Mesiah <sm...@gmail.com>.
+1 (non-binding)

I can verify that my changes for the Amazon and Snowflake providers for
this release wave are working as expected.

On Fri, 25 Sep 2026 at 09:50, Wei Lee <we...@apache.org> wrote:

> +1 (binding), checked:
>
> - SVN
> - in Docker installation
> - Reproducible package builds
> - Licence
> - Signature
> - Checksums
>
> Thanks!
>
> Best regards,
> Wei Lee
>
> On 2026/09/25 08:22:48 Pankaj Koti via dev wrote:
> > +1 non-binding
> >
> > Tested that my PRs are included in the RC and working as expected, thanks
> > for cutting the release!
> >
> > On Fri, Sep 25, 2026 at 3:32 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> > > +1 (binding)
> > >
> > > Checked:
> > >
> > > * SVN: all expected files present (check-release-files), and all 78 RC
> > >   providers install at their RC versions (Dockerfile.pmc)
> > > * Signatures: all 157 good (Shahar's key from KEYS)
> > > * Checksums: all 157 SHA512 good
> > > * Licences: Apache RAT 0.18 - 0 unapproved, 0 unknown
> > > * Reproducible builds: the source tarball and all 156 packages are
> > >   byte-identical when rebuilt from the providers/2026-09-22 tag with
> > >   flit 4.0.2
> > >
> > > One note on reproducibility, not a blocker: the wheels were built with
> > > flit 4.0.2, but dev/breeze/uv.lock at the tag locks flit 4.1.0. Since
> > > flit builds without isolation, rebuilding with the locked Breeze (as
> > > the docs say) gives 75 wheels that differ only in the "Generator:"
> > > line of their WHEEL file (and its hash in RECORD) - the packaged files
> > > are identical. I opened a PR explaining how to rebuild with the
> > > release manager's flit version:
> > > https://github.com/apache/airflow/pull/73699
> > >
> > > I also tested all my changes in this wave with all 78 RC providers
> > > installed from the PyPI wheels in Breeze (Airflow 3.3.2):
> > >
> > > * #72162 (amazon, google, microsoft.azure) - remote log uploads outside
> > >   base_log_folder are skipped, uploads inside still work
> > > * #72166 (google) - Drive q= values are escaped
> > > * #73413 (common.sql) - DataFusion error message shows the storage type
> > > * #72627 (edge3) - docs only, present in the release
> > > * #72174 (snowflake) and #72176 (teradata) - in the wave, though not
> > >   listed in the testing issue - both work as expected
> > >
> > > Improvement to the verification process:
> > >
> > > I tested all my changes with an agent using Apache Magpie's
> > > release-management
> > > "verify-rc" skill and a new Airflow override that adds an optional
> "test
> > > your own changes" step. The agent found my entries in the testing issue
> > > (and the two changes missing from it), verified each change is in the
> > > RC tags, changelogs and wheels, downloaded the whole wave and wrote a
> > > Dag exercising every change - I only had to start Breeze and trigger
> it.
> > > It also ran the regular checks above and tracked down the flit
> > > difference.
> > >
> > > That was a very good experience - I highly recommend trying it:
> > > https://github.com/apache/airflow/pull/73697
> > >
> > > J.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > For additional commands, e-mail: dev-help@airflow.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> For additional commands, e-mail: dev-help@airflow.apache.org
>
>

Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Wei Lee <we...@apache.org>.
+1 (binding), checked:

- SVN
- in Docker installation
- Reproducible package builds
- Licence
- Signature
- Checksums

Thanks!

Best regards,
Wei Lee

On 2026/09/25 08:22:48 Pankaj Koti via dev wrote:
> +1 non-binding
> 
> Tested that my PRs are included in the RC and working as expected, thanks
> for cutting the release!
> 
> On Fri, Sep 25, 2026 at 3:32 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> 
> > +1 (binding)
> >
> > Checked:
> >
> > * SVN: all expected files present (check-release-files), and all 78 RC
> >   providers install at their RC versions (Dockerfile.pmc)
> > * Signatures: all 157 good (Shahar's key from KEYS)
> > * Checksums: all 157 SHA512 good
> > * Licences: Apache RAT 0.18 - 0 unapproved, 0 unknown
> > * Reproducible builds: the source tarball and all 156 packages are
> >   byte-identical when rebuilt from the providers/2026-09-22 tag with
> >   flit 4.0.2
> >
> > One note on reproducibility, not a blocker: the wheels were built with
> > flit 4.0.2, but dev/breeze/uv.lock at the tag locks flit 4.1.0. Since
> > flit builds without isolation, rebuilding with the locked Breeze (as
> > the docs say) gives 75 wheels that differ only in the "Generator:"
> > line of their WHEEL file (and its hash in RECORD) - the packaged files
> > are identical. I opened a PR explaining how to rebuild with the
> > release manager's flit version:
> > https://github.com/apache/airflow/pull/73699
> >
> > I also tested all my changes in this wave with all 78 RC providers
> > installed from the PyPI wheels in Breeze (Airflow 3.3.2):
> >
> > * #72162 (amazon, google, microsoft.azure) - remote log uploads outside
> >   base_log_folder are skipped, uploads inside still work
> > * #72166 (google) - Drive q= values are escaped
> > * #73413 (common.sql) - DataFusion error message shows the storage type
> > * #72627 (edge3) - docs only, present in the release
> > * #72174 (snowflake) and #72176 (teradata) - in the wave, though not
> >   listed in the testing issue - both work as expected
> >
> > Improvement to the verification process:
> >
> > I tested all my changes with an agent using Apache Magpie's
> > release-management
> > "verify-rc" skill and a new Airflow override that adds an optional "test
> > your own changes" step. The agent found my entries in the testing issue
> > (and the two changes missing from it), verified each change is in the
> > RC tags, changelogs and wheels, downloaded the whole wave and wrote a
> > Dag exercising every change - I only had to start Breeze and trigger it.
> > It also ran the regular checks above and tracked down the flit
> > difference.
> >
> > That was a very good experience - I highly recommend trying it:
> > https://github.com/apache/airflow/pull/73697
> >
> > J.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > For additional commands, e-mail: dev-help@airflow.apache.org
> >
> >
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
For additional commands, e-mail: dev-help@airflow.apache.org


Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Pankaj Koti via dev <de...@airflow.apache.org>.
+1 non-binding

Tested that my PRs are included in the RC and working as expected, thanks
for cutting the release!

On Fri, Sep 25, 2026 at 3:32 AM Jarek Potiuk <ja...@potiuk.com> wrote:

> +1 (binding)
>
> Checked:
>
> * SVN: all expected files present (check-release-files), and all 78 RC
>   providers install at their RC versions (Dockerfile.pmc)
> * Signatures: all 157 good (Shahar's key from KEYS)
> * Checksums: all 157 SHA512 good
> * Licences: Apache RAT 0.18 - 0 unapproved, 0 unknown
> * Reproducible builds: the source tarball and all 156 packages are
>   byte-identical when rebuilt from the providers/2026-09-22 tag with
>   flit 4.0.2
>
> One note on reproducibility, not a blocker: the wheels were built with
> flit 4.0.2, but dev/breeze/uv.lock at the tag locks flit 4.1.0. Since
> flit builds without isolation, rebuilding with the locked Breeze (as
> the docs say) gives 75 wheels that differ only in the "Generator:"
> line of their WHEEL file (and its hash in RECORD) - the packaged files
> are identical. I opened a PR explaining how to rebuild with the
> release manager's flit version:
> https://github.com/apache/airflow/pull/73699
>
> I also tested all my changes in this wave with all 78 RC providers
> installed from the PyPI wheels in Breeze (Airflow 3.3.2):
>
> * #72162 (amazon, google, microsoft.azure) - remote log uploads outside
>   base_log_folder are skipped, uploads inside still work
> * #72166 (google) - Drive q= values are escaped
> * #73413 (common.sql) - DataFusion error message shows the storage type
> * #72627 (edge3) - docs only, present in the release
> * #72174 (snowflake) and #72176 (teradata) - in the wave, though not
>   listed in the testing issue - both work as expected
>
> Improvement to the verification process:
>
> I tested all my changes with an agent using Apache Magpie's
> release-management
> "verify-rc" skill and a new Airflow override that adds an optional "test
> your own changes" step. The agent found my entries in the testing issue
> (and the two changes missing from it), verified each change is in the
> RC tags, changelogs and wheels, downloaded the whole wave and wrote a
> Dag exercising every change - I only had to start Breeze and trigger it.
> It also ran the regular checks above and tracked down the flit
> difference.
>
> That was a very good experience - I highly recommend trying it:
> https://github.com/apache/airflow/pull/73697
>
> J.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> For additional commands, e-mail: dev-help@airflow.apache.org
>
>

Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Jarek Potiuk <ja...@potiuk.com>.
+1 (binding)

Checked:

* SVN: all expected files present (check-release-files), and all 78 RC
  providers install at their RC versions (Dockerfile.pmc)
* Signatures: all 157 good (Shahar's key from KEYS)
* Checksums: all 157 SHA512 good
* Licences: Apache RAT 0.18 - 0 unapproved, 0 unknown
* Reproducible builds: the source tarball and all 156 packages are
  byte-identical when rebuilt from the providers/2026-09-22 tag with
  flit 4.0.2

One note on reproducibility, not a blocker: the wheels were built with
flit 4.0.2, but dev/breeze/uv.lock at the tag locks flit 4.1.0. Since
flit builds without isolation, rebuilding with the locked Breeze (as
the docs say) gives 75 wheels that differ only in the "Generator:"
line of their WHEEL file (and its hash in RECORD) - the packaged files
are identical. I opened a PR explaining how to rebuild with the
release manager's flit version: https://github.com/apache/airflow/pull/73699

I also tested all my changes in this wave with all 78 RC providers
installed from the PyPI wheels in Breeze (Airflow 3.3.2):

* #72162 (amazon, google, microsoft.azure) - remote log uploads outside
  base_log_folder are skipped, uploads inside still work
* #72166 (google) - Drive q= values are escaped
* #73413 (common.sql) - DataFusion error message shows the storage type
* #72627 (edge3) - docs only, present in the release
* #72174 (snowflake) and #72176 (teradata) - in the wave, though not
  listed in the testing issue - both work as expected

Improvement to the verification process:

I tested all my changes with an agent using Apache Magpie's release-management
"verify-rc" skill and a new Airflow override that adds an optional "test
your own changes" step. The agent found my entries in the testing issue
(and the two changes missing from it), verified each change is in the
RC tags, changelogs and wheels, downloaded the whole wave and wrote a
Dag exercising every change - I only had to start Breeze and trigger it.
It also ran the regular checks above and tracked down the flit
difference.

That was a very good experience - I highly recommend trying it:
https://github.com/apache/airflow/pull/73697

J.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
For additional commands, e-mail: dev-help@airflow.apache.org


Re: [VOTE] Airflow Providers, release preparation date 2026-09-22

Posted by Shahar Epstein <sh...@apache.org>.
Thanks Aaron and Subhramit!

Also, forgot to mention in the highlights - we have a release candidate for
a new provider, DuckDB!
Thanks to Niko for introducing it - I'll appreciate the community's help
with testing it as well :)


Shahar

On Thu, Sep 24, 2026 at 3:30 PM Shahar Epstein <sh...@apache.org> wrote:

> Hey all,
>
> I have just cut the new wave Airflow Providers packages with release
> preparation date 2026-09-22. This email is calling a vote on the release,
> which will last for an extended period of 5 days - which means that it
> will end on 2026-09-29 12:00 UTC, with at least 3 binding +1 votes required
> for the release to pass.
>
> Consider this my (binding) +1.
> General highlights
>
>    - This wave includes many providers. Fun fact: there were so many that
>    I had to split the testing GitHub issue in two! This is mainly due to the
>    work on #35259, which adds connection ID templating across all providers.
>    - Work on #70296 is nearly complete, with a few exceptions (in
>    practice I resolved the issue). It moves template-field validation and
>    transformation out of __init__ so they run after template rendering,
>    preventing errors caused by processing unrendered values.
>    - We hope to graduate common.ai to 1.0.0 in the next RC, whether in a
>    wave or an ad hoc release. I'd like to ask the community's attention to
>    test this provider’s 0.10.0 RC extensively, as it includes many changes.
>    - To allow an appropriate time for testing all providers (in
>    particular: common.ai, fab, google, and amazon) - I extend the usualy
>    release vote period in extra two days than usual.
>
> Breaking changes and upgrade notes
>
>    - *edge3 4.3.2 → 5.0.0:* EdgeExecutor now counts queued workloads
>    against [core] parallelism. Review this setting if you rely on higher
>    concurrency (#72048).
>    - *git 0.5.0 → 1.0.0:* Token authentication now uses a credential
>    helper configured through GIT_CONFIG_COUNT and requires Git ≥ 2.31 on
>    Dag processors and workers (#64105).
>    - *microsoft.psrp 3.2.7 → 4.0.0:* PsrpOperator no longer defaults
>    task_id to the cmdlet; pass task_id explicitly (#73036).
>    - *openai 1.8.2 → 2.0.0:* create_embeddings now returns a list of
>    embedding vectors for list inputs, rather than only the first vector. This
>    also changes the XCom returned by OpenAIEmbeddingOperator for those
>    inputs (#71989).
>    - *common.ai <http://common.ai> 0.9.0 → 0.10.0:* PydanticAI vendor
>    connection types change from hyphens to underscores; SQLToolset now
>    rejects allowed_tables=None and allowed_tables=[] (omit the argument
>    to allow all tables); and execute_complete overrides on LLMOperator
>    and LLMBranchOperator must accept decision=None (#72853, #73381,
>    #73452, #73368).
>    - *Amazon:* Deferrable operators and sensors now pass their AWS
>    region, TLS verification, and botocore settings to triggers (#72171).
>    FTP/SFTP–S3 transfers now match filename prefixes rather than substrings
>    (#73269).
>
> Deprecations
>
>    - *Google Cloud Stackdriver:* Stackdriver components are renamed to
>    Cloud Monitoring and Cloud Logging (#73354, #73575). The Stackdriver*
>    operators, StackdriverHook, and Stackdriver links move to the new
>    CloudMonitoring* classes in the cloud_monitoring modules. The
>    Stackdriver task log handler becomes CloudLoggingTaskHandler in
>    cloud_logging_task_handler. The old names still work but emit
>    deprecation warnings; they are planned for removal after March 31, 2027.
>    - *Google Cloud Pub/Sub:* The default for return_immediately is
>    deprecated (#73504). PubSubPullOperator, PubSubPullSensor, and
>    PubsubPullTrigger now warn when return_immediately is not set. This
>    also applies to Google Pub/Sub asset watchers. The default will change from
>    True to False in the first Google provider major release after March
>    31, 2027. To preserve the current behavior, pass
>    return_immediately=True. The deferrable PubSubPullSensor now respects
>    this argument; previously, it dropped it, so the trigger always ran with
>    True.
>    - *Amazon QuickSight:* QuickSightHook.wait_for_state is deprecated in
>    favor of wait_for_ingestion, and the operator’s check_interval is
>    deprecated in favor of waiter_delay (#70218). No removal date has been
>    set.
>
>
>
> Airflow Providers are available at:
> https://dist.apache.org/repos/dist/dev/airflow/providers/2026-09-22
>
> *apache-airflow-providers-2026-09-22-source.tar.gz* is the full source
> tarball of airflow repo - snapshot taken at the moment of provider's
> release.
>
> *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the convenience python
> "sdist" distributions that we publish in PyPI
>
> *apache_airflow_providers_<PROVIDER>-*.whl are the convenience Python
> "wheel" distributions that we publish in PyPI.
>
> The test procedure for PMC members is described in
>
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-pmc-members
>
> The test procedure for and Contributors who would like to test this RC is
> described in:
>
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-contributors
>
>
> Public keys are available at:
> https://dist.apache.org/repos/dist/release/airflow/KEYS
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Only votes from PMC members are binding, but members of the community are
> encouraged to test the release and vote with "(non-binding)".
>
> Please note that the version number excludes the 'rcX' string.
> This will allow us to rename the artifact without modifying
> the artifact checksums when we actually release it.
>
> The status of testing the providers by the community is kept here:
> https://github.com/apache/airflow/issues/73658 - Part 1
> https://github.com/apache/airflow/issues/73658#issuecomment-5813334599 -
> Part 2
>
> The issue is also the easiest way to see important PRs included in the RC
> candidates.
> Detailed changelog for the providers will be published in the
> documentation after the
> RC candidates are released.
>
> You can find the RC packages in PyPI following these links:
>
> https://pypi.org/project/apache-airflow-providers-airbyte/6.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-alibaba/3.5.0rc1/
> https://pypi.org/project/apache-airflow-providers-amazon/9.37.0rc1/
> https://pypi.org/project/apache-airflow-providers-anthropic/1.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-beam/6.3.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-druid/4.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-flink/1.9.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.14.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-hive/9.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-kylin/3.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-livy/4.6.2rc1/
> https://pypi.org/project/apache-airflow-providers-apache-pig/4.9.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-apache-tinkerpop/1.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-apprise/2.4.0rc1/
> https://pypi.org/project/apache-airflow-providers-arangodb/2.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-asana/2.12.0rc1/
> https://pypi.org/project/apache-airflow-providers-atlassian-jira/3.4.0rc1/
> https://pypi.org/project/apache-airflow-providers-celery/3.24.1rc1/
> https://pypi.org/project/apache-airflow-providers-cloudant/4.3.6rc1/
>
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.23.0rc1/
> https://pypi.org/project/apache-airflow-providers-cohere/1.8.0rc1/
> https://pypi.org/project/apache-airflow-providers-common-ai/0.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-common-compat/1.20.0rc1/
> https://pypi.org/project/apache-airflow-providers-common-io/1.10.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-common-messaging/2.1.1rc1/
> https://pypi.org/project/apache-airflow-providers-common-sql/2.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-databricks/7.21.0rc1/
> https://pypi.org/project/apache-airflow-providers-datadog/3.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-dbt-cloud/4.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-dingding/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-docker/4.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-duckdb/0.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-edge3/5.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-exasol/4.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-fab/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-ftp/3.16.0rc1/
> https://pypi.org/project/apache-airflow-providers-git/1.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-github/2.12.0rc1/
> https://pypi.org/project/apache-airflow-providers-google/22.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-grpc/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-hashicorp/4.8.2rc1/
> https://pypi.org/project/apache-airflow-providers-http/6.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-imap/3.13.0rc1/
> https://pypi.org/project/apache-airflow-providers-influxdb/2.12.0rc1/
> https://pypi.org/project/apache-airflow-providers-keycloak/0.11.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-microsoft-azure/15.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-microsoft-psrp/4.0.0rc1/
>
> https://pypi.org/project/apache-airflow-providers-microsoft-winrm/3.15.0rc1/
> https://pypi.org/project/apache-airflow-providers-mongo/5.5.0rc1/
> https://pypi.org/project/apache-airflow-providers-mysql/6.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-neo4j/3.13.0rc1/
> https://pypi.org/project/apache-airflow-providers-openai/2.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-openlineage/2.20.2rc1/
> https://pypi.org/project/apache-airflow-providers-opensearch/1.13.0rc1/
> https://pypi.org/project/apache-airflow-providers-opsgenie/5.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-oracle/4.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-pagerduty/5.3.0rc1/
> https://pypi.org/project/apache-airflow-providers-pinecone/2.5.0rc1/
> https://pypi.org/project/apache-airflow-providers-postgres/7.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-presto/5.13.0rc1/
> https://pypi.org/project/apache-airflow-providers-qdrant/1.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-redis/4.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-salesforce/5.15.0rc1/
> https://pypi.org/project/apache-airflow-providers-samba/4.14.0rc1/
> https://pypi.org/project/apache-airflow-providers-segment/3.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-sftp/6.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-slack/9.11.0rc1/
> https://pypi.org/project/apache-airflow-providers-smtp/3.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-snowflake/6.18.0rc1/
> https://pypi.org/project/apache-airflow-providers-ssh/6.1.0rc1/
> https://pypi.org/project/apache-airflow-providers-standard/1.20.0rc1/
> https://pypi.org/project/apache-airflow-providers-tableau/5.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-telegram/4.10.0rc1/
> https://pypi.org/project/apache-airflow-providers-teradata/3.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-trino/6.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-weaviate/3.5.0rc1/
> https://pypi.org/project/apache-airflow-providers-yandex/4.6.0rc1/
>
> Sincerely,
> Shahar Epstein
>