Hmm. I am not sure if this was accidental, but there are a lot of files with double-extenssions (.asc.asc etc.) in the SVN folder. I do not think it invalidates the vote (i am still checking the regular ones) - but they should be removed.
On Wed, Jul 8, 2026 at 7:41 PM Buğra Öztürk <[email protected]> wrote: > Thanks for the release, Vincent! > > +1 (binding). I have checked SVN, In Docker installation, Reproducible > package builds, Licence, Signature and Checksums. They look good. > > Best regards, > Bugra Ozturk > > On Wed, Jul 8, 2026 at 1:16 PM Aaron Chen <[email protected]> wrote: > > > +1 (non-binding) > > > > I tested the following provider RCs in a Breeze environment (Airflow > 3.1.3, > > Python 3.10, Postgres backend): > > - apache-airflow-providers-anthropic==0.1.0rc1 > > - apache-airflow-providers-common-ai[openai,mcp]==0.6.0rc1 > > - apache-airflow-providers-google==22.2.2rc1 > > - apache-airflow-providers-openai==1.8.0rc1 > > - apache-airflow-providers-openlineage==2.19.0rc1 > > > > I installed the RC packages into Breeze and ran a set of smoke-test DAGs > > exercising each provider's hooks/operators e2e against live > > OpenAI/Anthropic/GCP accounts, with OpenLineage emitting events to a > local > > Marquez instance. > > > > Results: > > - openlineage: DAG ran successfully end-to-end, events received by > Marquez. > > - google: BigQueryHook.get_records() executed a real query against > BigQuery > > and returned the expected result. > > - openai: hook correctly reaches the OpenAI API; the only failure was an > > account-level `insufficient_quota` (429), not a provider defect. > > - anthropic: hook correctly reaches the Anthropic API; the only failure > was > > an account-level low credit balance (400), not a provider defect. > > - common-ai[openai]: PydanticAIHook correctly reaches the OpenAI backend > > via the provider; blocked by the same account-level quota issue as the > > openai provider above, not a provider defect. > > > > Cheers, > > Aaron > > > > On Wed, Jul 8, 2026 at 6:46 PM Wei Lee <[email protected]> wrote: > > > > > +1 (binding), checked: > > > > > > - SVN > > > - in Docker installation > > > - Reproducible build > > > - Licence > > > - Signature > > > - Checksums > > > > > > Best regards, > > > Wei Lee > > > > > > Amogh Desai <[email protected]> 於 2026年7月8日週三 下午1:42寫道： > > > > > > > +1 binding. > > > > > > > > - Performed svn checks > > > > - Reproducible package build checks > > > > - License checks > > > > - Signature checks > > > > - SHA512 checks > > > > > > > > Installed the bits and tested with breeze and validated my changes, > > along > > > > with > > > > a few general purpose dags. Looks good. > > > > > > > > Thanks & Regards, > > > > Amogh Desai > > > > > > > > > > > > On Wed, Jul 8, 2026 at 3:56 AM Niko Oliveira <[email protected]> > > > wrote: > > > > > > > > > +1 (binding) > > > > > > > > > > I ran the suite of Amazon provider package system tests on the > build > > > and > > > > > all were green: > > > > > > > > > > > > > > > > > > > > https://aws-mwaa.github.io/#/open-source/system-tests/version/a050861fc59193347a60d6ab306a5e0a03c719a7_9.32.0rc1.html > > > > > I also checked SVN files, the reproducible build, license and > > signature > > > > > checks, and sha512 > > > > > > > > > > Cheers, > > > > > Niko > > > > > > > > > > On Tue, Jul 7, 2026 at 9:59 AM Vincent Beck <[email protected]> > > > wrote: > > > > > > > > > > > Hey all, > > > > > > > > > > > > I have just cut the new wave Airflow Providers packages with > > release > > > > > > preparation date 2026-07-06. This email is calling a vote on the > > > > release, > > > > > > which will last for 72 hours - which means that it will end on > > > > 2026-07-10 > > > > > > 16:06 UTC and until 3 binding +1 votes have been received. > > > > > > > > > > > > > > > > > > Consider this my (binding) +1. > > > > > > > > > > > > Important callouts: > > > > > > - apache-airflow-providers-postgres. Even though this provider is > > > > > included > > > > > > in this email, it will be skipped and released in the next wave > > > > instead. > > > > > > The reason is that PR > https://github.com/apache/airflow/pull/69526 > > > is > > > > > not > > > > > > yet merged and will most likely be released in the next wave. > Since > > > > this > > > > > is > > > > > > a breaking change (thus, a major version bump), and we already > have > > > > > another > > > > > > PR with a breaking change for this provider in this release wave > ( > > > > > > https://github.com/apache/airflow/pull/69089), we decided with > > Iliya > > > > > Romm > > > > > > to postpone it to the next provider release so we only ship one > > major > > > > > > version upgrade instead of two. See the Slack thread for more > > details > > > > > here: > > > > > > > > > > > > https://apache-airflow.slack.com/archives/C03G9H97MM2/p1783358970674109 > > > > > > > > > > > > Airflow Providers are available at: > > > > > > > > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/airflow/providers/$\{RELEASE_DATE\} > > > > > > > > > > > > *apache-airflow-providers-2026-07-06-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/69562 > > > > > > > > > > > > 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/5.5.2rc1/ > > > > > > > > https://pypi.org/project/apache-airflow-providers-amazon/9.32.0rc1/ > > > > > > > > > https://pypi.org/project/apache-airflow-providers-anthropic/0.1.0rc1/ > > > > > > > > https://pypi.org/project/apache-airflow-providers-celery/3.22.0rc1/ > > > > > > > > > https://pypi.org/project/apache-airflow-providers-common-ai/0.6.0rc1/ > > > > > > > > > > > > > > > > > > > > > https://pypi.org/project/apache-airflow-providers-common-compat/1.16.0rc1/ > > > > > > > > > https://pypi.org/project/apache-airflow-providers-common-sql/2.0.2rc1/ > > > > > > > > > > > > https://pypi.org/project/apache-airflow-providers-databricks/7.17.0rc1/ > > > > > > > https://pypi.org/project/apache-airflow-providers-edge3/4.1.0rc1/ > > > > > > > > > > > > > > > > > > > > > https://pypi.org/project/apache-airflow-providers-elasticsearch/6.8.0rc1/ > > > > > > > > https://pypi.org/project/apache-airflow-providers-exasol/4.10.4rc1/ > > > > > > https://pypi.org/project/apache-airflow-providers-fab/3.7.2rc1/ > > > > > > https://pypi.org/project/apache-airflow-providers-ftp/3.15.2rc1/ > > > > > > https://pypi.org/project/apache-airflow-providers-git/0.4.1rc1/ > > > > > > > > https://pypi.org/project/apache-airflow-providers-google/22.2.2rc1/ > > > > > > > https://pypi.org/project/apache-airflow-providers-imap/3.12.0rc1/ > > > > > > > > > > > > > > > > > > > > > > > > > > > https://pypi.org/project/apache-airflow-providers-microsoft-azure/13.5.1rc1/ > > > > > > > > > > > > > > > > > > > > > > > > > > > https://pypi.org/project/apache-airflow-providers-microsoft-winrm/3.14.4rc1/ > > > > > > > https://pypi.org/project/apache-airflow-providers-neo4j/3.12.0rc1/ > > > > > > > https://pypi.org/project/apache-airflow-providers-openai/1.8.0rc1/ > > > > > > > > > > > > https://pypi.org/project/apache-airflow-providers-openlineage/2.19.0rc1/ > > > > > > > > > > > > https://pypi.org/project/apache-airflow-providers-opensearch/1.11.0rc1/ > > > > > > > https://pypi.org/project/apache-airflow-providers-oracle/4.6.2rc1/ > > > > > > > > https://pypi.org/project/apache-airflow-providers-postgres/7.0.0rc1/ > > > > > > https://pypi.org/project/apache-airflow-providers-smtp/3.0.2rc1/ > > > > > > > > > https://pypi.org/project/apache-airflow-providers-snowflake/6.15.0rc1/ > > > > > > https://pypi.org/project/apache-airflow-providers-ssh/5.0.4rc1/ > > > > > > > > > https://pypi.org/project/apache-airflow-providers-standard/1.16.0rc1/ > > > > > > > > https://pypi.org/project/apache-airflow-providers-tableau/5.6.0rc1/ > > > > > > > > > > > > > > > > > > Cheers, > > > > > > Vincent Beck > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > >
