Hey fellow Airflowers,

I am cancelling this vote due to a few issues found in rc1. I will create
rc2 soon for testing.
Regards,
Rahul Vats

On Wed, 1 Apr 2026 at 00:32, Buğra Öztürk <[email protected]> wrote:

> Awesome news! Great work, Rahul and everyone who contributed!
> (+1 binding) I have checked and verified below for both Apache Airflow
> 3.2.0rc1 and Task SDK 1.2.0rc1,
> - Reproducible package builds
> - SVN
> - Licence
> - Signature
> - Checksums
>
> I have built the images locally, started Airflow, and run a couple of
> example DAGs. Everything looks good overall.
>
> I have not yet had time to dig deeper or run more complex tests. To be
> clear, the main verification checks are passing. The initial startup of
> components works, DAG operations such as parsing and running behave as
> expected, and nothing looked suspicious in the logs when using Breeze with
> SAM (SimpleAuthManager with Admin).
>
> I also needed to delete the
> `airflow/airflow-core/src/airflow/ui/.pnpm-store` directory because it
> showed differences after building with my local `hatch`. I removed the
> directory and used the image approach. The script showed no difference
> afterwards. After checking with diffoscope, it seems that the UI compiled
> assets need to be fully regenerated. I am leaving this note here in case
> someone else runs into the same issue.
>
> Best regards,
> Bugra Ozturk
>
>
> On Tue, Mar 31, 2026 at 7:54 AM Amogh Desai <[email protected]> wrote:
>
> > Wooh, brilliant work Rahul and everyone else who contributed to this
> > release.
> >
> >
> > Thanks & Regards,
> > Amogh Desai
> >
> >
> > On Tue, Mar 31, 2026 at 5:32 AM Jarek Potiuk <[email protected]> wrote:
> >
> > > Cool!
> > >
> > > On Tue, Mar 31, 2026 at 1:44 AM Vikram Koka via dev <
> > > [email protected]>
> > > wrote:
> > >
> > > > Outstanding work, Rahul, and everyone who contributed to this
> release.
> > > > I am looking forward to trying this out over the next couple of days!
> > > >
> > > > Vikram
> > > >
> > > > On Mon, Mar 30, 2026 at 3:07 PM Rahul Vats <[email protected]>
> > > wrote:
> > > >
> > > > > Hey fellow Airflowers,
> > > > >
> > > > > The release candidates for Apache Airflow 3.2.0rc1 and Task SDK
> > > 1.2.0rc1
> > > > > are now available for testing!
> > > > >
> > > > > This email is calling for a vote on the release, which will last at
> > > least
> > > > > 72 hours, from Monday, March 30, 2026 at 10:00 PM UTC
> > > > > until Thrusday, April 2, 2026 at 10:00 PM (UTC)
> > > > > <
> > > > >
> > > > >
> > > >
> > >
> >
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=8&iso=20260402T22&p1=1440
> > > > > >,
> > > > > and until 3 binding +1 votes have been received.
> > > > >
> > > > > Consider this my +1 binding vote.
> > > > >
> > > > > Airflow 3.2.0rc1 is available at:
> > > > > https://dist.apache.org/repos/dist/dev/airflow/3.2.0rc1/
> > > > >
> > > > > "apache-airflow" Meta package:
> > > > > - *apache-airflow-3.2.0-source.tar.gz* is a source release that
> comes
> > > > with
> > > > > INSTALL instructions.
> > > > > - *apache-airflow-3.2.0.tar.gz* is the binary Python "sdist"
> release.
> > > > > - *apache_airflow-3.2.0-py3-none-any.whl* is the binary Python
> wheel
> > > > > "binary" release.
> > > > >
> > > > > "apache-airflow-core" package:
> > > > > - *apache_airflow_core-3.2.0.tar.gz* is the binary Python "sdist"
> > > > release.
> > > > > - *apache_airflow_core-3.2.0-py3-none-any.whl* is the binary Python
> > > wheel
> > > > > "binary" release.
> > > > >
> > > > > Task SDK 1.2.0 is available at:
> > > > > https://dist.apache.org/repos/dist/dev/airflow/task-sdk/1.2.0rc1/
> > > > >
> > > > > "apache-airflow-task-sdk" package:
> > > > > - *apache_airflow_task_sdk-1.2.0.tar.gz* is the binary Python
> "sdist"
> > > > > release.
> > > > > - *apache_airflow_task_sdk-1.2.0-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.0 for Airflow package and 1.2.0 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.0
> > > > >
> > > > > Release Notes:
> > > > > -
> https://github.com/apache/airflow/blob/3.2.0rc1/RELEASE_NOTES.rst
> > > > > -
> > > > >
> > > > >
> > > >
> > >
> >
> https://airflow.staged.apache.org/docs/apache-airflow/3.2.0/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.0rc1 \
> > > > >   apache-airflow-core==3.2.0rc1 \
> > > > >   apache-airflow-task-sdk==1.2.0rc1
> > > > >
> > > > > Constraints files are at
> > > > > https://github.com/apache/airflow/tree/constraints-3.2.0rc1
> > > > >
> > > > > Regards,
> > > > > Rahul Vats
> > > > >
> > > >
> > >
> >
>

Reply via email to