Cancelling this vote due to issue
https://github.com/apache/airflow/issues/71367 noticed during testing. I
will get rc2 out soon.

Regards,
Rahul Vats



On Sun, 9 Aug 2026 at 13:58, Jarek Potiuk <[email protected]> wrote:

> Just to add a little to what Rahul wrote - this was a "complicated" release
> where we attempted (and eventually succeeded) to have parallel releases of
> Airflow + Providers - actually we had 3 (!) parallel releases (2 for
> providers and one for Airflow).
> We also added manually triggerable workflows in CI to rebuild/refresh
> constraints for the RC and final releases, which should give us flexibility
> so we will not have to "sequentialize" those in the future. We also solved
> a few long-time standing issues:
>
> * it "assures" that constraints have been refreshed **just** before
> releasing airflow as part of RM workflow
> * we had protection against accidental downgrades of providers because
> resolution of `--highest` made decision than another package "highest" was
> more important. But that required "guessing" what caused the problem (it
> happened once already and it was a head-scratcher that required me to guess
> what kind of workaround to apply. With those fixes now it "pins" the latest
> providers and will complain if that causes some conflicts—a much better
> error
>
> Greetings from Bejing.
>
> J.
>
>
> On Sun, Aug 9, 2026 at 1:57 PM Rahul Vats <[email protected]> wrote:
>
> > Update on the Python 3.14 issue from earlier- it is now resolved.
> >
> > constraints have been regenerated and all Python images (including 3.14)
> > have been rebuilt with the latest providers, including
> > apache-airflow-providers-google 22.3.0rc4 which carries the fix. 3.14 is
> > now
> > fully testable.
> >
> > Thanks to Jarek for cutting google 22.3.0rc4 quickly and fixing the
> release
> > constraints
> > workflow.
> >
> > Regards,
> > Rahul Vats
> >
> > On Fri, 7 Aug 2026 at 15:42, Rahul Vats <[email protected]> wrote:
> >
> > > Hey fellow Airflowers,
> > >
> > > The release candidates for Apache Airflow 3.3.1rc1 and Task SDK
> 1.3.1rc1
> > > are now available for testing!
> > >
> > > This email is calling for a vote on the release, which will last at
> least
> > > until *12th Aug 2026* and until 3 binding +1 votes have been received.
> > > Consider this my +1 binding vote.
> > >
> > > Status of testing for this release is tracked in
> > >  https://github.com/apache/airflow/issues/71274
> > > <https://github.com/apache/airflow/issues/71274>
> > >
> > > Airflow 3.3.1rc1 is available at:
> > > https://dist.apache.org/repos/dist/dev/airflow/3.3.1rc1/
> > >
> > > "apache-airflow" Meta package:
> > > - *apache-airflow-3.3.1-source.tar.gz* is a source release that comes
> > with
> > > INSTALL instructions.
> > > - *apache-airflow-3.3.1.tar.gz* is the binary Python "sdist" release.
> > > - *apache_airflow-3.3.1-py3-none-any.whl* is the binary Python wheel
> > > "binary" release.
> > >
> > > "apache-airflow-core" package:
> > > - *apache_airflow_core-3.3.1.tar.gz* is the binary Python "sdist"
> > release.
> > > - *apache_airflow_core-3.3.1-py3-none-any.whl* is the binary Python
> wheel
> > > "binary" release.
> > >
> > > Task SDK 1.3.1 is available at:
> > > https://dist.apache.org/repos/dist/dev/airflow/task-sdk/1.3.1rc1/
> > >
> > > "apache-airflow-task-sdk" package:
> > > - *apache_airflow_task_sdk-1.3.1.tar.gz* is the binary Python "sdist"
> > > release.
> > > - *apache_airflow_task_sdk-1.3.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.3.1 for Airflow package and 1.3.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.3.1
> > >
> > > Release Notes:
> > > - https://github.com/apache/airflow/blob/3.3.1rc1/RELEASE_NOTES.rst
> > > -
> > >
> >
> https://airflow.staged.apache.org/docs/apache-airflow/3.3.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.3.1rc1 \
> > >   apache-airflow-core==3.3.1rc1 \
> > >   apache-airflow-task-sdk==1.3.1rc1
> > >
> > > Constraints files are at
> > > https://github.com/apache/airflow/tree/constraints-3.3.1rc1
> > >
> > > *Note:*
> > > Python 3.14 image build is currently failing. Installing the Google
> > > provider
> > > (apache-airflow-providers-google) on 3.14 fails to resolve -
> > > google-cloud-aiplatform's
> > > "evaluation" extra caps litellm to a range that does not support 3.14
> > yet.
> > > This is an
> > > upstream issue. Jarek is already on it and plans to release a new
> google
> > > provider rc
> > > (rc4) today, once that is out I will rebuild the constraints and the
> 3.14
> > > image and
> > > update this thread.
> > >
> > > This only affects the Google provider on 3.14. The core apache-airflow
> > and
> > > Task SDK
> > > packages install and run fine there, so please still test 3.14 and just
> > > leave the
> > > Google provider out for now.
> > >
> > > Cheers,
> > > Rahul
> > >
> >
>

Reply via email to