+1 non-binding. Tested with regression DAGs and new bug fixes, all looks good!
Regards, Rahul Vats On Mon, 27 Oct 2025 at 13:00, Amogh Desai <[email protected]> wrote: > +1 binding. > > For both airflow-core 3.1.1RC2 and task-sdk 1.1.1RC2: > - Checked reproducible package builds > - Performed SVN checks > - Checked Licenses > - Checked Signatures > - Checked SHA512 checksums > > Installed the RC and ran a couple of random example dags from my > test set, all of them work fine. Also ran a quick check to see if my > changes > are working as expected, all good. > > On Sat, Oct 25, 2025 at 11:49 PM Jens Scheffler <[email protected]> > wrote: > > > Hi, > > > > thanks Kaxil for preparing the release! > > > > 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 found one UI glitch, not sure whether this is worth stopping and > > cutting a new release: I used breeze to start Airflow 3.1.1rc2 and > > previously had FabAuthManager, switched for the tests to > > SimpleAuthManager and login is not possible. Needed to delete the > > "_token" manually from Cookies. > > > > Tested the 3.1.1rc2 with EdgeExecutor and I was able to run the > > Integration Test Dag via Breeze like usual. All seems to be working. > > > > In my view: Let's have it released! > > > > Jens > > > > On 24.10.25 22:04, Jarek Potiuk wrote: > > > Cool. Verified it again - same sources were used and thanks to > > > reproducibility check we know it. > > > > > > Changing my vote on task-sdk to: +1 (binding) task-sdk: checked SVN, > > DOcker > > > install, licences, signatures, checksums, reproducibility > > > > > > > > > On Fri, Oct 24, 2025 at 8:31 PM Kaxil Naik <[email protected]> > wrote: > > > > > >> re-published task-sdk/1.1.1rc2 on SVN now from the same sources. > > >> > > >> On Fri, 24 Oct 2025 at 17:03, Jarek Potiuk <[email protected]> wrote: > > >> > > >>> +1 (binding) airflow+airflow-core: checked SVN, DOcker install, > > licences, > > >>> signatures, checksums, reproducibility > > >>> -1 (binding) task-sdk: checked SVN, DOcker install, licences, > > signatures, > > >>> checksums, reproducibility > > >>> > > >>> Unfortunately reproducibility checks failed and it turned out that > the > > >>> task-sdk. tar.gz in SVN contains some uv cache files : > > >>> > > >>> -rw-r--r-- 0/0 1 2025-10-22 03:43 > > >>> apache_airflow_task_sdk-1.1.1/.uv-cache/.gitignore > > >>> -rwxr-xr-x 0/0 0 2025-10-22 03:43 > > >>> apache_airflow_task_sdk-1.1.1/.uv-cache/.lock > > >>> -rw-r--r-- 0/0 43 2025-10-22 03:43 > > >>> apache_airflow_task_sdk-1.1.1/.uv-cache/CACHEDIR.TAG > > >>> -rw-r--r-- 0/0 9922 2025-10-22 03:43 > > >>> > > >>> > > >> > > > apache_airflow_task_sdk-1.1.1/.uv-cache/interpreter-v4/7e11d242fb84b9e8/f9fdec8ae1355b5c.msgpack > > >>> -rw-r--r-- 0/0 0 2025-10-22 03:43 > > >>> apache_airflow_task_sdk-1.1.1/.uv-cache/sdists-v9/.git > > >>> -rw-r--r-- 0/0 0 2025-10-22 03:43 > > >>> apache_airflow_task_sdk-1.1.1/.uv-cache/sdists-v9/.gitignore > > >>> > > >>> This is because the ".uv-cache" folder has been stored in the source > > code > > >>> of Release Manager's task-sdk. I think it's worth to re-release it. > > >>> > > >>> I also finally followed added task-sdk steps for our release process, > > >> they > > >>> were missing. I refreshed the release steps and updated our checks > and > > >>> .rat-excludes to use the new rat 0.17. It also adds .gitignore that > > >> should > > >>> allow Release Manager to build the same package without .uv-cache > files > > >>> even if they are locally created. > > >>> > > >>> PR here -> https://github.com/apache/airflow/pull/57203 > > >>> > > >>> J. > > >>> > > >>> > > >>> On Fri, Oct 24, 2025 at 2:57 AM Dheeraj Turaga < > > [email protected]> > > >>> wrote: > > >>> > > >>>> +1 from me (non-binding) > > >>>> > > >>>> I tested the release with breeze —use-airflow-version 3.1.1rc2 and > > >> things > > >>>> look good > > >>>> > > >>>> On Thu, Oct 23, 2025 at 12:19 PM Kaxil Naik <[email protected]> > > >> wrote: > > >>>>> Hey fellow Airflowers, > > >>>>> > > >>>>> The release candidates for *Apache Airflow 3.1.1rc2 *and *Task SDK > > >>>>> 1.1.1rc2* are > > >>>>> now available for testing! > > >>>>> > > >>>>> This email is calling for a vote on the release, which will last at > > >>> least > > >>>>> until *27th Oct* and until 3 binding +1 votes have been received. > > >>>>> > > >>>>> Consider this my +1 binding vote. > > >>>>> > > >>>>> Airflow 3.1.1rc2 is available at: > > >>>>> https://dist.apache.org/repos/dist/dev/airflow/3.1.1rc2/ > > >>>>> > > >>>>> "apache-airflow" Meta package: > > >>>>> > > >>>>> - *apache-airflow-3.1.1-source.tar.gz* is a source release that > > >>> comes > > >>>>> with INSTALL instructions. > > >>>>> - *apache-airflow-3.1.1.tar.gz* is the binary Python "sdist" > > >>> release. > > >>>>> - *apache_airflow-3.1.1-py3-none-any.whl* is the binary Python > > >> wheel > > >>>>> "binary" release. > > >>>>> > > >>>>> > > >>>>> "apache-airflow-core" package > > >>>>> > > >>>>> - *apache_airflow_core-3.1.1.tar.gz* is the binary Python > "sdist" > > >>>>> release. > > >>>>> - *apache_airflow_3.1.1-py3-none-any.whl* is the binary Python > > >> wheel > > >>>>> "binary" release. > > >>>>> > > >>>>> > > >>>>> Task SDK 1.1.1rc2 is available at: > > >>>>> https://dist.apache.org/repos/dist/dev/airflow/task-sdk/1.1.1rc2/ > > >>>>> > > >>>>> "apache-airflow-task-sdk" package > > >>>>> > > >>>>> - *apache_airflow_task_sdk-1.1.1.tar.gz* is the binary Python > > >>> "sdist" > > >>>>> release. > > >>>>> - *apache_airflow_task_sdk-1.1.1-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.1.1 for Airflow package and 1.1.1 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.1.1 > > >>>>> *Release Notes*: > > >>>>> > > >>>>> - > https://github.com/apache/airflow/blob/3.1.1rc1/RELEASE_NOTES.rst > > >>>>> - > > >>>>> > > >>>>> > > >> > > > https://airflow.staged.apache.org/docs/apache-airflow/3.1.1/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.1.1rc2 \ > > >>>>> apache-airflow-core==3.1.1rc2 \ > > >>>>> apache-airflow-task-sdk==1.1.1rc2 > > >>>>> ``` > > >>>>> > > >>>>> Constraints files are at > > >>>>> https://github.com/apache/airflow/tree/constraints-3.1.1rc2 > > >>>>> > > >>>>> Regards, > > >>>>> Kaxil > > >>>>> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
