Hey fellow Airflowers, I have cut Airflow 2.10.4rc1. This email is calling a vote on the release, which will last at least 72 hours, from Tuesday, December 10, 2024 at 2:00 pm UTC until Friday, December 13, 2024 at 2:00 pm UTC <https://www.timeanddate.com/worldclock/fixedtime.html?msg=8&iso=20241213T1400&p1=1440>, and until 3 binding +1 votes have been received.
Status of testing of the release is kept in https://github.com/apache/airflow/issues/44811 Consider this my (non-binding) +1. As I’m not a member of the PMC, Ephraim signed the distribution. Airflow 2.10.4rc1 is available at: https://dist.apache.org/repos/dist/dev/airflow/2.10.4rc1/ *apache-airflow-2.10.4-source.tar.gz* is a source release that comes with INSTALL instructions. *apache-airflow-2.10.4.tar.gz* is the binary Python "sdist" release. *apache_airflow-2.10.4-py3-none-any.whl* is the binary Python wheel "binary" release. Public keys are available at: https://dist.apache.org/repos/dist/release/airflow/KEYS Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Only votes from PMC members are binding, but all members of the community are encouraged to test the release and vote with "(non-binding)". The test procedure for PMC members is described in: https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md\#verify-the-release-candidate-by-pmc-members The test procedure for contributors and members of the community who would like to test this RC is described in: https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md\#verify-the-release-candidate-by-contributors Please note that the version number excludes the `rcX` string, so it's now simply 2.10.4. This will allow us to rename the artifact without modifying the artifact checksums when we actually release. Release Notes: https://github.com/apache/airflow/blob/2.10.4rc1/RELEASE_NOTES.rst For information on what goes into a release please see: https://github.com/apache/airflow/blob/main/dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md *Changes since 2.10.3:* *Significant Changes** TaskInstance ``priority_weight`` is capped in 32-bit signed integer ranges (#43611)* Some database engines are limited to 32-bit integer values. As some users reported errors in weight rolled-over to negative values, we decided to cap the value to the 32-bit integer. Even if internally in python smaller or larger values to 64 bit are supported, ``priority_weight`` is capped and only storing values from -2147483648 to 2147483647. *Bug Fixes* - Fix stats of dynamic mapped tasks after automatic retries of failed tasks (#44300) - Fix wrong display of multi-line messages in the log after filtering (#44457) - Allow "/" in metrics validator (#42934) (#44515) - Fix gantt flickering (#44488) (#44517) - Fix problem with inability to remove fields from Connection form (#40421) (#44442) - Check pool_slots on partial task import instead of execution (#39724) (#42693) - Avoid grouping task instance stats by try_number for dynamic mapped tasks (#44300) (#44319) - Re-queue task when they are stuck in queued (#43520) (#44158) - Suppress the warnings where we check for sensitive values (#44148) (#44167) - Fix get_task_instance_try_details to return appropriate schema (#43830) (#44133) - Log message source details are grouped (#43681) (#44070) - Fix duplication of Task tries in the UI (#43891) (#43950) - Add correct mime-type in OpenAPI spec (#43879) (#43901) - Disable extra links button if link is null or empty (#43844) (#43851) - Disable XCom list ordering by execution_date (#43680) (#43696) - Fix venv numpy example which needs to be 1.26 at least to be working in Python 3.12 (#43659) - Fix Try Selector in Mapped Tasks also on Index 0 (#43590) (#43591) - Prevent using ``trigger_rule="always"`` in a dynamic mapped task (#43810) - Prevent using ``trigger_rule=TriggerRule.ALWAYS`` in a task-generated mapping within bare tasks (#44751) *Doc Only Changes* - Update XCom docs around containers/helm (#44570) (#44573) *Miscellaneous* - Raise deprecation warning when accessing inlet or outlet events through str (#43922) Cheers, Utkarsh Sharma
