TL;DR; In short - we are looking for candidates to join our security
team. Please send a message to priv...@airflow.apache.org if you would like
to be added to the team.
Following our rotation process:
https://github.com/apache/airflow/blob/223a741869505ad31c38310f307bf2f0f0f193fb/contributing
Thanks, Jarek, for this proposal. Overall, I really like it—it significantly
simplifies multi-team support and removes the need to deploy additional
components per team, without compromising on the core needs of users (unless
I’m missing something).
> And if we do it and implement packaging and
Lazy consensus reached. Merging. Welcome @TJaniF + @m1racoli !
On 10.06.25 23:58, Jens Scheffler wrote:
Hi Devs,
alongside and after VOTE of the new i18 policy and aiming to follow
the new policy as beta tester I'd like to suggest and invite
- @TJaniF
- @m1racoli
... as additional German N
On Fri, Jun 13, 2025 at 7:09 PM Vincent Beck wrote:
> Thanks, Jarek, for this proposal. Overall, I really like it—it
> significantly simplifies multi-team support and removes the need to deploy
> additional components per team, without compromising on the core needs of
> users (unless I’m missing
The vote to release Apache Airflow Python Client 3.0.2 from 3.0.2rc1 has
now passed.
3 "+1" binding votes received:
- Kaxil Naik
- Jens Scheffler
- Jarek Potiuk
Vote thread:
https://lists.apache.org/thread/r3hz4dc3rqgzx4z8pwnkwnvzldxyhvbw
I'll continue with the release process, and the release a
Dear Airflow community,
I'm happy to announce that Apache Airflow Python Client 3.0.2 was just
released.
We made this version available on PyPI for convenience:
`pip install apache-airflow-client==3.0.2`
https://pypi.org/project/apache-airflow-client/3.0.2/
The documentation is available at:
ht
OK. I spent some time thinking about it, I had to go back to the
drawing board - which required me to clean my head of many of the previous
assumptions and I think I figured out how we can provide "9+%" of what - at
least I heard from the users who asked for it without adding the complexity
that ri
Hello everyone,
As you might know, Airflow 2 has a long-time issue with not being able to
upgrade Werkzeug dependency to a non-vulnerable version and that raises a
lot of alarms for users who run CVE checks on Airflow.
We've been waiting for a long time for that - but it looks like there is a
lig
