Agree with Jens, is the bug affecting something at runtime? Or is it just
class naming?

Thanks & Regards,
Amogh Desai


On Fri, May 22, 2026 at 11:02 AM Jens Scheffler <[email protected]> wrote:

> Hi Sameer,
>
> can you share more details of the bug? Is there a fix PR or issue ticket
> describing? Then I/we can decide if we make a RC2 depending on severity.
>
> Jens
>
> On 22.05.26 00:43, Sameer Mesiah wrote:
> > + 1 (non-binding) for this release wave (with a caveat).
> >
> > I have verified the changes I introduced in the following provider
> packages:
> >
> > apache-airflow-providers-airbyte==5.5.0rc1
> > apache-airflow-providers-dbt-cloud==4.9.0rc1
> > apache-airflow-providers-elasticsearch==6.5.4rc1
> > apache-airflow-providers-imap==3.11.3rc1
> >
> > The caveat is that I identified 2 bugs of the same class in
> > apache-airflow-providers-airbyte==5.5.0rc1 and
> > apache-airflow-providers-dbt-cloud==4.9.0rc1.
> >
> > The bug in the Airbyte provider was already present but the bug in the
> DBT
> > Cloud provider has been introduced in this release wave.
> >
> > If possible, I would recommend the preparation of a second release
> > candidate (RC2) for the aforementioned providers, which will include
> fixes
> > for both.
> >
> > Thanks,
> > Sameer Mesiah.
> >
> > On Thu, 21 May 2026 at 09:39, Amogh Desai <[email protected]> wrote:
> >
> >> +1 binding.
> >>
> >> - Checked SVN
> >> - Checked reproducible package builds
> >> - Checked licences
> >> - Checked signatures
> >> - Checked SHA512 checks
> >>
> >> I didn't have changes in this wave, so this is more of a PMC check.
> >>
> >> Thanks & Regards,
> >> Amogh Desai
> >>
> >>
> >> On Thu, May 21, 2026 at 1:22 AM Oliveira, Niko <[email protected]>
> >> wrote:
> >>
> >>> +1 (non-binding)
> >>>
> >>> Here is the AWS system tests run against the RC candidate:
> >>>
> >>
> https://aws-mwaa.github.io/#/open-source/system-tests/version/3047ad7fa3cbb8d442840111bed7febfab0a767e_9.29.0rc1.html
> >>> The single failure is a known issue currently with the system test
> >> itself,
> >>> not the operator.
> >>>
> >>> Cheers,
> >>> Niko
> >>> ________________________________
> >>> From: Vincent Beck <[email protected]>
> >>> Sent: Wednesday, May 20, 2026 7:26 AM
> >>> To: [email protected] <[email protected]>
> >>> Subject: RE: [EXT] [VOTE] Airflow Providers, release preparation date
> >>> 2026-05-19
> >>>
> >>> CAUTION: This email originated from outside of the organization. Do not
> >>> click links or open attachments unless you can confirm the sender and
> >> know
> >>> the content is safe.
> >>>
> >>>
> >>>
> >>> AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur
> externe.
> >>> Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne
> >> pouvez
> >>> pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain
> >> que
> >>> le contenu ne présente aucun risque.
> >>>
> >>>
> >>>
> >>> +1 binding. Checked:
> >>>
> >>> * SVN
> >>> * Reproducible package builds
> >>> * Licence
> >>> * Signature
> >>> * SHA512
> >>>
> >>> On 2026/05/20 08:14:47 Wei Lee wrote:
> >>>>    +1 (binding), checked:
> >>>>
> >>>>    - SVN
> >>>>    - in Docker installation
> >>>>    - Reproducible package builds
> >>>>    - Licence
> >>>>    - Signature
> >>>>    - Checksums
> >>>>
> >>>>    Best regards,
> >>>>    Wei Lee
> >>>>
> >>>> Shahar Epstein <[email protected]> 於 2026年5月20日週三 下午2:57寫道:
> >>>>
> >>>>> +1 (binding), checked:
> >>>>>
> >>>>> - SVN
> >>>>> - Reproducible build
> >>>>> - Licenses
> >>>>> - Signatures
> >>>>> - Checksums
> >>>>>
> >>>>> Thanks Aaron for voting and testing the providers!
> >>>>>
> >>>>>
> >>>>> Shahar
> >>>>>
> >>>>> On Wed, May 20, 2026 at 1:01 AM Jens Scheffler <[email protected]>
> >>>>> wrote:
> >>>>>> Hey all,
> >>>>>>
> >>>>>> I have just cut the new wave Airflow Providers packages with
> >> release
> >>>>>> preparation date 2026-05-19. This email is calling a vote on the
> >>>>>> release, which will last for 72 hours - which means that it will
> >> end
> >>> on
> >>>>>> 2026-05-22 21:50 UTC and until 3 binding +1 votes have been
> >> received.
> >>>>>> Consider this my (binding) +1.
> >>>>>>
> >>>>>> This is a standard cut of 46 providers release including all
> >>> providers
> >>>>>> which had changes since the last release cycle.
> >>>>>>
> >>>>>> Airflow Providers are available at:
> >>>>>>
> >> https://dist.apache.org/repos/dist/dev/airflow/providers/2026-05-19
> >>>>>> *apache-airflow-providers-2026-05-19-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/67213
> >>>>>>
> >>>>>> 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.0rc1/
> >> https://pypi.org/project/apache-airflow-providers-alibaba/3.3.8rc1/
> >> https://pypi.org/project/apache-airflow-providers-amazon/9.29.0rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.12.0rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-hive/9.5.0rc1/
> >>
> https://pypi.org/project/apache-airflow-providers-apache-kafka/1.14.0rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-livy/4.5.6rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-spark/6.0.2rc1/
> >> https://pypi.org/project/apache-airflow-providers-celery/3.20.0rc1/
> >>
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.17.1rc1/
> >>> https://pypi.org/project/apache-airflow-providers-common-ai/0.3.0rc1/
> >>
> https://pypi.org/project/apache-airflow-providers-common-compat/1.15.0rc1/
> >>> https://pypi.org/project/apache-airflow-providers-common-sql/2.0.0rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-databricks/7.15.0rc1/
> >>> https://pypi.org/project/apache-airflow-providers-dbt-cloud/4.9.0rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-docker/4.5.6rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-edge3/3.7.0rc1/
> >>>>>>
> >>
> https://pypi.org/project/apache-airflow-providers-elasticsearch/6.5.4rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-fab/3.6.4rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-ftp/3.15.0rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-git/0.4.0rc1/
> >>>>>>
> >> https://pypi.org/project/apache-airflow-providers-google/22.0.0rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-imap/3.11.3rc1/
> >>>>>>
> >>> https://pypi.org/project/apache-airflow-providers-influxdb/2.11.0rc1/
> >> https://pypi.org/project/apache-airflow-providers-keycloak/0.7.2rc1/
> >>
> https://pypi.org/project/apache-airflow-providers-microsoft-azure/13.3.0rc1/
> >>
> https://pypi.org/project/apache-airflow-providers-microsoft-mssql/4.6.0rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-mongo/5.4.0rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-mysql/6.6.0rc1/
> >>>>>>
> >>>
> https://pypi.org/project/apache-airflow-providers-openlineage/2.17.0rc1/
> >>> https://pypi.org/project/apache-airflow-providers-opensearch/1.9.2rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-oracle/4.6.0rc1/
> >>>>>>
> >> https://pypi.org/project/apache-airflow-providers-pinecone/2.4.5rc1/
> >> https://pypi.org/project/apache-airflow-providers-postgres/6.7.0rc1/
> >> https://pypi.org/project/apache-airflow-providers-presto/5.12.0rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-sftp/5.8.0rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-smtp/3.0.1rc1/
> >>>>>>
> >>> https://pypi.org/project/apache-airflow-providers-snowflake/6.13.0rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-ssh/5.0.2rc1/
> >>>>>>
> >>> https://pypi.org/project/apache-airflow-providers-standard/1.13.1rc1/
> >> https://pypi.org/project/apache-airflow-providers-tableau/5.4.1rc1/
> >> https://pypi.org/project/apache-airflow-providers-teradata/3.6.0rc1/
> >>>>>> https://pypi.org/project/apache-airflow-providers-trino/6.6.0rc1/
> >>>>>>
> >> https://pypi.org/project/apache-airflow-providers-vertica/4.4.0rc1/
> >> https://pypi.org/project/apache-airflow-providers-weaviate/3.3.4rc1/
> >> https://pypi.org/project/apache-airflow-providers-zendesk/4.12.0rc1/
> >>>>>> Cheers,
> >>>>>> Jens Scheffler
> >>>>>>
> >>>>>>
> >>>>>>
> >> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: [email protected]
> >>>>>> For additional commands, e-mail: [email protected]
> >>>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: [email protected]
> >>>>> For additional commands, e-mail: [email protected]
> >>>>>
> >>>>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [email protected]
> >>> For additional commands, e-mail: [email protected]
> >>>
> >>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to