62261 for sure, hard month to compete against that beautiful registry.
________________________________
From: Briana Steel via dev <[email protected]>
Sent: Wednesday, March 25, 2026 10:16 AM
To: [email protected] <[email protected]>
Cc: Briana Steel <[email protected]>
Subject: [EXT] [VOTE] March 2026 PR of the Month

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you can confirm the sender and know the 
content is safe.



AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. Ne 
cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez pas 
confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que le 
contenu ne présente aucun risque.



Hey All,

It's once again time to vote for the PR of the Month!

With the help of the get_important_pr_candidates script in dev/stats,
we've identified the following candidates:

PR#53216: Feat: Add version change indicators for Dag and bundle
versions in Grid view by @choo121600 (Yeonguk Choo)
https://github.com/apache/airflow/pull/53216

PR#62261: Add Apache Airflow Provider Registry by @kaxil (Kaxil Naik)
https://github.com/apache/airflow/pull/62261

PR#63520: Python 3.14 Support by @Dev-iL
https://github.com/apache/airflow/pull/63520

PR#62924: Support Python 3.13 in fab provider by @Dev-iL
https://github.com/apache/airflow/pull/62924

PR#62664: Replace connexion with FastAPI for FAB provider by @1Ninad
(Ninad Kale) https://github.com/apache/airflow/pull/62664

Please reply to this thread with your selection or offer your own nominee(s).

Voting will close on Friday at 10 AM PST. The winner(s) will be
featured in the next issue of the Airflow newsletter.

Also, if there's an article or event that you think should be included
in this or a future issue of the newsletter, please drop me a line at
[email protected].

-- Briana Steel

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to