Go for it On Fri, 23 Oct 2026 at 18:31, Shahar Epstein <[email protected]> wrote:
> Hey everyone, > > airflowctl 0.1.5 shipped in early June. Since then, the > airflow-ctl/v0-1-test branch has collected more > than 30 backported fixes, and some of them affect users directly. > > Buğra, who built the airflowctl release process and ran every release so > far, has been away since the summer. > To help keep things moving in the meantime, I am volunteering to act as > release manager for the next airflowctl version. > On that note I'd like to thank Buğra for his work, and hope that he will be > able to return to the community soon. > > We have tried to release airflowctl 1.0.0 twice. In October 2025 we > cancelled the 1.0.0rc1 and 1.0.0rc2 votes > and moved to 0.x, to keep room for breaking changes [1]. In June 2026 Buğra > proposed 1.0.0 again [2], but the > vote never started. PyPI does not accept a version twice, so the next 1.0.0 > candidate must be 1.0.0rc3. > > Proposed plan: > > 1. Release 0.1.6 from airflow-ctl/v0-1-test, with fixes only. It works with > Airflow 3.2, 3.3 and 3.4 servers. > 2. Before the RC, get CI running on airflow-ctl/v0-1-test (#70724). Today > the branch runs only the ASF > allowlist check. > 3. Stop backporting features to airflow-ctl/v0-1-test. New commands and > breaking changes stay on main. > 4. Release main after Airflow 3.4.0 GA, because its client needs a 3.4 > server. That release can be 0.2.0, or > 1.0.0 (starting from 1.0.0rc3) if we agree the CLI is stable. I will > start a separate thread for that choice. > > Unless there are objections, I will start preparing 0.1.6rc1 soon. > If you have anything related to propose or discuss, I'll appreciate if you > could do it in this thread. > If anyone else wants to assist in the release process, feel free to get in > touch! > At last, I'd like to thank Wei for helping with some pre-requisites. > > [1] https://lists.apache.org/thread/bppcy5mfzjyc9g8rn84bssqk3srlmdht > [2] https://lists.apache.org/thread/0g2lh6so0b3y02ojhzglt1y7vngmfdfj > > > Thanks, > Shahar >
