-1 (binding) - at least for now. It passes the verification but when
testing airflow locally - I found out that Graph view does not refresh
while tasks are running, Sounds like basic feature and I think if it is
reproduced by others,

It's quite a blocker IMHO (if reproducible); it could only be me though - I
see the same on Airflow 3.2.0 and main. I added some more info to the
issue. If this is something easily explainable with my setup, I am happy to
change it to +1.

Created https://github.com/apache/airflow/issues/65517. with video showing
what's going on.

Verified:

    - reproducible-build: all 7 packages byte-identical to SVN
    - svn:                all 21 expected files present
    - licenses:           8625 AL + 3 MIT, 0 unapproved / 0 unknown (Apache
RAT)
    - signatures:         all 7 .asc signatures valid
                          (signed by Rahul Vats <[email protected]>)
    - checksums:          all 7 SHA512 checksums match

  Packages verified:
    apache_airflow-3.2.1-source.tar.gz
    apache_airflow-3.2.1.tar.gz
    apache_airflow-3.2.1-py3-none-any.whl
    apache_airflow_core-3.2.1.tar.gz
    apache_airflow_core-3.2.1-py3-none-any.whl
    apache_airflow_task_sdk-1.2.1.tar.gz
    apache_airflow_task_sdk-1.2.1-py3-none-any.whl

Thanks Rahul for the release work!


J.


On Sun, Apr 19, 2026 at 9:17 PM Buğra Öztürk <[email protected]>
wrote:

> +1 (binding) for both Apache Airflow and Task SDK
> I have checked and verified the following for both packages,
> - Reproducible package builds
> - SVN
> - Licence
> - Signature
> - Checksums
>
> Ran some example Dags with breeze played with as variables, connections and
> pools. Overall, looks good.
>
> On Sat, Apr 18, 2026 at 5:09 PM Jens Scheffler <[email protected]>
> wrote:
>
> > Hi Rahul,
> >
> > 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
> >
> > As we had the rc1 extensively tested including a load test I am quite
> > confident that this is good. inspected diff to rc2 and as the fix from
> > @AutomationDev is included did my normal release validation.
> >
> > Locally as well tested rc2 via breeze and using EdgeExecutor and my
> > usual integration test round. All looking good. Let's have it released!
> >
> > On 17.04.26 21:48, Rahul Vats wrote:
> > > Hey fellow Airflowers,
> > >
> > > The release candidates for Apache Airflow 3.2.1rc2 and Task SDK
> 1.2.1rc2
> > > are now available for testing!
> > >
> > > This email is calling for a vote on the release, which will last at
> least
> > > until *20th Apr* and until 3 binding +1 votes have been received.
> > > Consider this my +1 binding vote.
> > >
> > > Status of testing of the release is kept in
> > > https://github.com/apache/airflow/issues/65336
> > >
> > > Airflow 3.2.1rc2 is available at:
> > > https://dist.apache.org/repos/dist/dev/airflow/3.2.1rc2/
> > >
> > > "apache-airflow" Meta package:
> > > - *apache-airflow-3.2.1-source.tar.gz* is a source release that comes
> > with
> > > INSTALL instructions.
> > > - *apache-airflow-3.2.1.tar.gz* is the binary Python "sdist" release.
> > > - *apache_airflow-3.2.1-py3-none-any.whl* is the binary Python wheel
> > > "binary" release.
> > >
> > > "apache-airflow-core" package:
> > > - *apache_airflow_core-3.2.1.tar.gz* is the binary Python "sdist"
> > release.
> > > - *apache_airflow_core-3.2.1-py3-none-any.whl* is the binary Python
> wheel
> > > "binary" release.
> > >
> > > Task SDK 1.2.1 is available at:
> > > https://dist.apache.org/repos/dist/dev/airflow/task-sdk/1.2.1rc2/
> > >
> > > "apache-airflow-task-sdk" package:
> > > - *apache_airflow_task_sdk-1.2.1.tar.gz* is the binary Python "sdist"
> > > release.
> > > - *apache_airflow_task_sdk-1.2.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.2.1 for Airflow package and 1.2.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.2.1
> > >
> > > Release Notes:
> > > - https://github.com/apache/airflow/blob/3.2.1rc2/RELEASE_NOTES.rst
> > > - https://airflow.staged.apache.org/docs/apache-airflow/3.2
> > > .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.2.1rc2 \
> > >    apache-airflow-core==3.2.1rc2 \
> > >    apache-airflow-task-sdk==1.2.1rc2
> > >
> > > Constraints files are at
> > > https://github.com/apache/airflow/tree/constraints-3.2.1rc2
> > >
> > >
> > > Regards,
> > > Rahul Vats
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>

Reply via email to