Correction to the last message: duckdb will be released either as 0.1.2, or
0.2.0,
since 0.1.1 was used as well.


Shahar

On Tue, Sep 29, 2026 at 9:53 AM Shahar Epstein <[email protected]> wrote:

> Hello,
>
> A follow-up on the result above: the duckdb provider has also been excluded
> from this release.
>
> Unfortunately, apache-airflow-providers-duckdb 0.1.0 cannot be published
> to PyPI. The
> filename was probably used by an earlier, deleted incarnation of the
> project on PyPI,
> and PyPI never allows a filename to be reused.
> The provider will be released as 0.1.1 with a new release candidate.
>
> The edge3, cncf.kubernetes and duckdb providers will be released ad-hoc /
> in the next
> wave of providers.
>
> Thanks,
> Shahar Epstein
>
> On Tue, Sep 29, 2026 at 9:15 AM Shahar Epstein <[email protected]> wrote:
>
>> Hello,
>>
>> Apache Airflow Providers prepared on 2026-09-22 have been accepted.
>>
>> 3 "+1" binding votes received:
>> - Shahar Epstein
>> - Jarek Potiuk
>> - Wei Lee
>>
>> 4 "+1" non-binding votes received for the whole set:
>> - Aaron Chen
>> - Subhramit B.B.
>> - Pankaj Koti
>> - Sameer Mesiah
>>
>> 1 "+1" non-binding vote received for specific providers:
>> - PoAn Yang (amazon, apache.beam, google)
>>
>> "-1" votes received for specific providers:
>> - edge3: 1 binding (Shahar Epstein), 1 non-binding (PoAn Yang)
>> - cncf.kubernetes: 1 binding (Shahar Epstein)
>>
>> The providers edge3 and cncf.kubernetes have been excluded from the
>> release.
>> - edge3 5.0.0rc1: a regression from #72048 makes the scheduler crash on
>> startup
>>   with DetachedInstanceError while Edge task instances from a previous
>> scheduler
>>   are still queued or running. The fix is in #73832.
>> - cncf.kubernetes 10.23.0rc1: a regression, fixed in #73764.
>> The next RC candidates for those providers will be released [in the next
>> wave
>> of providers] or [as an ad-hoc release on their own with accelerated vote
>> period].
>>
>> Vote thread:
>> https://lists.apache.org/thread/d48o1d9wcwr5so8gnjc09383frgnf4po
>>
>> I'll continue with the release process, and the release announcement will
>> follow shortly.
>>
>> Sincerely,
>>
>>
>> Shahar Epstein
>>
>

Reply via email to