> HOWEVER, the file apache_airflow_client-3.1.6/NOTICE file is empty, which seems wrong
(-1) binding: Checked (and works): * SVN * Reproducibility * checksums * licences * installation * basic python client tests work with `start-airflow` But Rich is right :). Great catch Rich! Thanks a lot for that - we have some blind-spots apparently and having a watchful "external" eye looking at our release artifacts proves to be useful :) I think we will need to add a separate check for the content of the NOTICE files in our validation. It also made me look a bit more inside the generated artifacts and look at the verification procedure and I found that "docs" and "tests" were added to the .whl (they are not needed there - only in .sdist), and that our verification process was not nicely separated from publishing in our instructions: All of that (except adding NOTICE verification step - that will come as a separate POR) fixed in: https://github.com/apache/airflow/pull/60539 - so Ephraim, you might want to get rc2 soon with those included. I also created the issue about implementing verification and synchronisation of https://github.com/apache/airflow/issues/60540 - and marked it as "good first issue" - so anyone can get a stab on it, I described in detail what I think should be done there. J. On Wed, Jan 14, 2026 at 4:22 PM Rich Bowen <[email protected]> wrote: > > > On 2026/01/14 15:11:17 Ephraim Anierobi wrote: > > Hey fellow Airflowers, > > > > The release candidate for Apache Airflow Python Client 3.1.6rc1 is now > > available for testing! > > -1 (non-binding) > > * Verified signatures and hashes on the following files as per > https://apache.org/info/verification.html > - apache_airflow_client-3.1.6.tar.gz (SHA512, GPG signature) > - apache_airflow_python_client-3.1.6-source.tar.gz (SHA512, GPG > signature) > * Verified LICENSE > > HOWEVER, the file apache_airflow_client-3.1.6/NOTICE file is empty, which > seems wrong > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
