I ran the reproducible package builds checks and got "apache_airflow_ctl-0.1.2-py3-none-any.whl:Binary files apache_airflow_ctl-0.1.2-py3-none-any.whl and dist/apache_airflow_ctl-0.1.2-py3-none-any.whl differ". Since it is the first time for me to run these tests for airflowctl, can someone double check if this is a real issue or if I somehow did something wrong when running the tests.
On 2026/02/21 20:34:55 Jens Scheffler wrote: > +1 (binding) - Checked SVN, Checksums, Reproducible package build, > Licenses, Signatures > > Did just manical release tests w/o functionality of airflowctl > > On 21.02.26 00:34, Buğra Öztürk wrote: > > The release candidate for **Apache Airflow Ctl**: 0.1.2rc1 is now > > available for testing! > > > > This email is calling for a vote on the release, which will last at least > > until Wednesday, the 25th of February, 10 pm CET (added a bit more time to > > the default 72 hours) and until 3 binding +1 votes have been received. > > > > Consider this my +1 (binding) vote. > > > > The apache-airflow-ctl 0.1.2rc1 package is available at: > > > > https://dist.apache.org/repos/dist/dev/airflow/airflow-ctl/0.1.2rc1/ > > > > The "apache-airflow-ctl" packages are: > > > > - *apache_airflow_ctl-0.1.2-source.tar.gz* is a source release that > > comes with INSTALL instructions. > > - *apache_airflow_ctl-0.1.2.tar.gz* is the binary Python "sdist" > > release. > > - *apache_airflow_ctl-0.1.2-py3-none-any.whl* is the binary Python wheel > > "binary" release. > > > > > > 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 all members of the community > > are encouraged to test the release and vote with "(non-binding)". > > > > The test procedure for PMC members is described in: > > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOWCTL.md#verify-the-release-candidate-by-pmc-members > > > > > > The test procedure for contributors and members of the community who would > > like to test this RC is described in: > > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOWCTL.md#verify-the-release-candidate-by-contributors > > > > > > Please note that the version number excludes the 'rcX' string, so it's now > > simply 0.1.2 for the apache-airflow-ctl package. > > > > This will allow us to rename the artifact without modifying the artifact > > checksums when we actually release. > > > > *Docs* (for preview, RELEASE_NOTES will be avaiable in stable): > > https://airflow.staged.apache.org/docs/apache-airflow-ct can be released > > from mainl/0.1.2/index.html > > <https://airflow.staged.apache.org/docs/apache-airflow-ctl/0.1.2/index.html> > > *Release Notes* (I am sorry, I was a bit late to create and merge the > > RELEASE_NOTES because that part is still manual. It should be okay since it > > will end up in the docs as in the staging (release_notes.html > > <https://airflow.staged.apache.org/docs/apache-airflow-ctl/0.1.2/release_notes.html#airflowctl-0-1-2-2026-02-20>), > > in the release description when we add it to GitHub, and in the main. > > Advantage of releasing from the main branch :) ): > > https://github.com/apache/airflow/blob/main/airflow-ctl/RELEASE_NOTES.rst > > > > *Testing Instructions using PyPI*: > > > > The packages are available in PyPI: > > https://pypi.org/project/apache-airflow-ctl/0.1.2rc1/ > > > > You can build a virtualenv that installs this and other required packages > > like this: > > > > uv venv > > uv pip install -U apache-airflow-ctl==0.1.2rc1 > > > > Regards, > > Bugra Ozturk > > > > --------------------------------------------------------------------- > 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]
