Thanks @Jens Scheffler <[email protected]> for reporting this. Can confirm the scheduler crash on our dev environment post upgrade.
Regards, Shubham Raj On Sun, May 24, 2026 at 9:54 PM Rahul Vats <[email protected]> wrote: > Thanks for reporting Jens. > > I am cancelling this vote due to the above issue, and I will prepare an RC2 > release for testing soon. > > Regards, > Rahul Vats > > On Sat, 23 May 2026 at 02:36, Jens Scheffler <[email protected]> wrote: > > > Hi Rahul, et all! > > > > After some more testing in our corporate environment this afternoon I > > (unfortunately) need to change my vote to -1 (binding). > > > > I tested 3.2.2rc1 with Celery (3.19.0)+Edge(3.6.0) Executor and the > > scheduler crashes in: > > > > (psycopg2.errors.DatatypeMismatch) CASE types text and uuid cannot be > > matched > > > > in airflow/jobs/scheduler_job_runner.py, line 964 > > > > I assume this is caused by PR > > https://github.com/apache/airflow/pull/65711 (back-ported from > > https://github.com/apache/airflow/pull/65594) - taking a look at the > > code I assume this is a bug caused by Multiple executors hitting this. > > The UUID must be converted to str() in the CASE statement. > > > > Full details shared in Slack in > > https://apache-airflow.slack.com/archives/C03G9H97MM2/p1779480220822829 > > > > Jens > > > > On 21.05.26 22:17, Jens Scheffler wrote: > > > Hi Rahul, et al! > > > > > > Thanks for cuttiong the release. Wow, this is a big one! > > > > > > I checked and tested 3.2.2rc1 with current wave of providers, > > > especially Edge Executor and my Integration Test Dag - all looks > > > smooth. My contributions/fixes are validated. > > > > > > Airflow/Airflow Core: +1 (binding), checked: > > > - SVN > > > - Reproducible package build > > > - Licenses > > > - Signatures > > > - Checksums > > > - Install in Docker > > > - Source tarball > > > Task SDK: +1 (binding), checked: > > > - SVN > > > - Reproducible package build > > > - Licenses > > > - Signatures > > > - Checksums > > > - Install in Docker > > > > > > I will run the next days some more extensive tests, this is an > > > intermediate PMC check result. > > > > > > Jens > > > > > > On 21.05.26 12:45, Rahul Vats wrote: > > >> Hey fellow Airflowers, > > >> > > >> The release candidates for Apache Airflow 3.2.2rc1 and Task SDK > 1.2.2rc1 > > >> are now available for testing! > > >> > > >> This email is calling for a vote on the release, which will last at > > >> least > > >> 5 days, from Thursday, May 21, 2026 at 10:00 AM UTC > > >> until Tuesday, May 26, 2026 at 10:00 AM UTC > > >> < > > >> > > > https://www.timeanddate.com/worldclock/fixedtime.html?msg=8&iso=20260526T10&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/67282 > > >> <https://github.com/apache/airflow/issues/65336> > > >> Airflow 3.2.2rc1 is available at: > > >> https://dist.apache.org/repos/dist/dev/airflow/3.2.2rc1/ > > >> > > >> "apache-airflow" Meta package: > > >> - *apache-airflow-3.2.2-source.tar.gz* is a source release that comes > > >> with > > >> INSTALL instructions. > > >> - *apache-airflow-3.2.2.tar.gz* is the binary Python "sdist" release. > > >> - *apache_airflow-3.2.2-py3-none-any.whl* is the binary Python wheel > > >> "binary" release. > > >> > > >> "apache-airflow-core" package: > > >> - *apache_airflow_core-3.2.2.tar.gz* is the binary Python "sdist" > > >> release. > > >> - *apache_airflow_core-3.2.2-py3-none-any.whl* is the binary Python > > >> wheel > > >> "binary" release. > > >> > > >> Task SDK 1.2.2 is available at: > > >> https://dist.apache.org/repos/dist/dev/airflow/task-sdk/1.2.2rc1/ > > >> > > >> "apache-airflow-task-sdk" package: > > >> - *apache_airflow_task_sdk-1.2.2.tar.gz* is the binary Python "sdist" > > >> release. > > >> - *apache_airflow_task_sdk-1.2.2-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 3.2.2 for Airflow package and 1.2.2 for Task SDK. This will > > >> allow us > > >> to rename the artifact without modifying > > >> the artifact checksums when we actually release. > > >> > > >> Docs (for preview): > > >> https://airflow.staged.apache.org/docs/apache-airflow/3.2.2 > > >> > > >> Release Notes: > > >> - https://github.com/apache/airflow/blob/3.2.2rc1/RELEASE_NOTES.rst > > >> - > > >> > > > https://airflow.staged.apache.org/docs/apache-airflow/3.2.2/release_notes.html > > >> > > >> (Rendered HTML) > > >> > > >> Testing Instructions using PyPI: > > >> You can build a virtualenv that installs this and other required > > >> packages > > >> (e.g. task sdk), like this: > > >> > > >> uv venv > > >> uv pip install -U \ > > >> apache-airflow==3.2.2rc1 \ > > >> apache-airflow-core==3.2.2rc1 \ > > >> apache-airflow-task-sdk==1.2.2rc1 > > >> > > >> Constraints files are at > > >> https://github.com/apache/airflow/tree/constraints-3.2.2rc1 > > >> > > >> > > >> Regards, > > >> Rahul Vats > > >> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > >
