Oh, this month again a real challenge to pick _one_ only. There are so many cool PRs merged last month. Feels like the list of achievements of the last half-year!

My +1 goes to #58365 because this really is a cool improvement and I learned something new just by reading the PR! But all others are really close-by!

As I am missing the Rookie PR list, from email hostory, thanks to Jed, I made a selection via
https://github.com/apache/airflow/pulls?q=is%3Apr+%22Awesome+work%2C+congrats+on+your+first+merged+pull+request%21%22+merged%3A%3E2025-12-01+is%3Aclosed+

...and not to have too many emails (if we do any) Rookie PR I'd favor the PR #59313 which added Japanese translations to UI.

Jens

On 1/12/26 23:38, Briana Steel via dev wrote:
Hey All,

It’s once again time to vote for the PR of the Month! Vote is a bit late as
I have been away.

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

PR#58365: Fix LocalExecutor memory spike by applying gc.freeze
https://github.com/apache/airflow/pull/58365

PR#55467: Enhance code view to support search and diff
https://github.com/apache/airflow/pull/55467

PR#58548: Add UI E2E testing framework with Playwright and Breeze
integration
https://github.com/apache/airflow/pull/58548

PR#56920: Add filters to Task Instances Tab
https://github.com/apache/airflow/pull/56920

PR#59183: fix(asset-parition): add a mutex lock to AssetModel when updating
APDR
https://github.com/apache/airflow/pull/59183

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

Voting will close on Friday, January 16th 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