+1 (binding)

Verified:
- Signature (Bugra's key) and SHA512 checksums on the SVN artifacts — all
good.
- Reproducible build from the airflow-ctl/0.1.5rc1 tag — wheel, sdist and
-source.tar.gz byte-for-byte identical to SVN (re-pushed bits check out).
- Live end-to-end smoke test: installed apache-airflow-ctl and exercised
airflowctl against a standalone Airflow API — auth, dags list, pools list,
connections list all worked.
- Confirmed the uv 0.11.8 floor bump (#66057) is present in the RC.

One headless-auth gotcha worth noting: airflowctl auth login with
username/password needs an OS keyring backend, which a container doesn't
have — the headless path is to mint a token with `airflowctl auth token`
and export AIRFLOW_CLI_TOKEN. Opened
https://github.com/apache/airflow/pull/67897 to document that and add a
dev/ helper that runs the contributor smoke test non-interactively.

Thanks Bugra!

Cheers,
Jarek

On Tue, Jun 2, 2026 at 12:42 AM Jens Scheffler <[email protected]> wrote:

> Thanks Bugra for fixing SVN - as no change in binaries and checks are OK
> no need to RC2 in my view. Still voting for the same bits and content.
>
> +1 (binding) - Checked SVN, Checksums, Reproducible package build,
> Licenses, Signatures
>
> Jens
>
> On 01.06.26 21:12, Buğra Öztürk wrote:
> > Hello all,
> >
> > First of all, sorry for the problematic SVN packages!
> >
> > I have fixed the SVN directory with artifacts from the created Tag (
> > `airflow-ctl/0.1.5rc1`
> > <https://github.com/apache/airflow/tree/airflow-ctl/0.1.5rc1>) again. If
> > someone thinks we would need RC2, please shout :)
> >
> > I realised I didn't provide the correct date. I would suggest Wednesday
> at
> > 7:00 PM CEST, considering the RC was created on Friday. This would also
> > allow enough time for a proper recheck.
> > Please verify when you have time again. Many thanks!
> >
> > Best regards,
> > Bugra Ozturk
> >
> > On Mon, Jun 1, 2026 at 6:27 PM Buğra Öztürk <[email protected]>
> wrote:
> >
> >> Hello Jens,
> >>
> >> Thanks for spotting! I totally missed while creating. My brained assumed
> >> added suffix empty while creating distribution and ignored the fact.
> Maybe
> >> I used old version of document or similar. I will fix it immediately.
> >>
> >> Best regards,
> >> Bugra Ozturk
> >>
> >> Op vr 29 mei 2026, 12:23 schreef Jens Scheffler <[email protected]>:
> >>
> >>> Hi Bugra,
> >>>
> >>> thanks for preparing the new release!
> >>>
> >>> Just wanted to write "+1" but then realized that the binaries fushed to
> >>> SVN have the "rc1" suffix being added. Usually we push the binaries as
> >>> the final and only rc1 to Pypi. Can you fix this? So until then a -1 as
> >>> PMC check.
> >>>
> >>> Jens
> >>>
> >>> On 28.05.26 18:36, Buğra Öztürk wrote:
> >>>> The release candidate for **Apache Airflow Ctl**: 0.1.5rc1  is now
> >>>> available for testing!
> >>>>
> >>>> This email is calling for a vote on the release, which will last at
> >>> least
> >>>> until the
> >>>> DATE_HERE and until 3 binding +1 votes have been received.
> >>>>
> >>>> Consider this my +1 (binding) vote.
> >>>>
> >>>> The apache-airflow-ctl 0.1.5rc1 package is available at:
> >>>> https://dist.apache.org/repos/dist/dev/airflow/airflow-ctl/0.1.5rc1/
> >>>>
> >>>> The "apache-airflow-ctl" packages are:
> >>>>
> >>>>      - *apache_airflow_ctl-0.1.5-source.tar.gz* is a source release
> that
> >>> comes
> >>>>        with INSTALL instructions.
> >>>>      - *apache_airflow_ctl-0.1.5.tar.gz* is the binary Python "sdist"
> >>> release.
> >>>>      - *apache_airflow_ctl-0.1.5-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.5 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):
> >>>>
> >>>
> https://airflow.staged.apache.org/docs/apache-airflow-ctl/0.1.5/index.html
> >>>> *Release Notes*:
> >>>>
> >>>
> https://github.com/apache/airflow/blob/airflow-ctl/0.1.5rc1/airflow-ctl/RELEASE_NOTES.rst
> >>>> *Testing Instructions using PyPI*:
> >>>>
> >>>> The packages are available in PyPI:
> >>>> https://pypi.org/project/apache-airflow-ctl/0.1.5rc1/
> >>>>
> >>>> 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.5rc1
> >>>>
> >>>> 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]
>
>

Reply via email to