Hey fellow Airflowers,

I'm cancelling this vote due to the above issue and will create an rc2 soon

- Ephraim

On Tue, 3 Feb 2026 at 06:54, Amogh Desai <[email protected]> wrote:

> +1 binding.
>
> - Checked SVN
> - Checked in Docker
> - Checked reproducible package builds
> - Checked licenses
> - Checked signatures
>
> Installed the RC and ran some of my test dags.
> It looks like there is an issue with pyjwt that we fixed via:
> https://github.com/apache/airflow/pull/61331
> as Jarek mentioned, so I'd let you take the call on it since it's for
> cases when constraints aren't used.
>
> Thanks & Regards,
> Amogh Desai
>
>
> On Mon, Feb 2, 2026 at 7:13 PM Jarek Potiuk <[email protected]> wrote:
>
> > 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
> >
> > However - there is the issue with PyJWT 2.11.0 that introduced more
> > validations on JWT tokens which was a breaking change for us (
> > https://github.com/apache/airflow/pull/61331) - this means that if
> someone
> > install now 3.1.7 without constraints, airflow will not work for them
> (see
> > https://github.com/apache/airflow/issues/61255#issuecomment-3832704070).
> > My
> > suggestion would be to have rc2 to avoid users bombarding us with issues.
> >
> > J.
> >
> >
> >
> > On Sun, Feb 1, 2026 at 11:48 AM Jens Scheffler <[email protected]>
> > wrote:
> >
> > > 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
> > >
> > > Did my usual round with the Integration Test Dag and Edge Executor and
> > > found one litch in the version check in EdgeExecutor related to RC
> > > versions. But this is no problem blocking the release but just
> something
> > > as a problem for the release checks itself. Reported as issue
> > > https://github.com/apache/airflow/issues/61313
> > >
> > > Also found a small UI glitch in missing translations keys, reported as
> > > issue https://github.com/apache/airflow/issues/61314. But also this is
> > > very minor, in my view not blocking to release.
> > >
> > > On 30.01.26 15:47, Shahar Epstein wrote:
> > > > +1 (binding), checked according to the manual instructions:
> > > >
> > > > - Reproducible package build
> > > > - SVN
> > > > - Licences
> > > > - Signatures
> > > > - Checksums
> > > >
> > > > Validated PRs that I authored/backported from main.
> > > >
> > > > In addition, I ran the experimental automated checks using the new
> > > command
> > > > and got the same successful result:
> > > > breeze release-management verify-rc-by-pmc --distribution airflow
> > > --version
> > > > 3.1.7rc1 --task-sdk-version 1.1.7rc1 --path-to-airflow-svn
> > > > ~/asf-dist/dev/airflow
> > > >
> > > > Other PMCs are welcome to try out the automation and report their
> > > > experience.
> > > > If you do so, please make sure to do the following before running the
> > > > command:
> > > > 0. Run the manual steps first, as the automation is still
> experimental.
> > > > 1. Update the --path-to-airflow-svn according to the path on your
> > machine
> > > > 2. Fetch git tags manually, otherwise the reproducible build step
> fails
> > > > (might be added to the automation later).
> > > >
> > > >
> > > > Shahar
> > > >
> > > >
> > > > On Fri, Jan 30, 2026 at 2:02 PM Ephraim Anierobi <
> > > [email protected]>
> > > > wrote:
> > > >
> > > >> Hey fellow Airflowers,
> > > >>
> > > >> The release candidates for Apache Airflow 3.1.7rc1 and Task SDK
> > 1.1.7rc1
> > > >> are now available for testing!
> > > >>
> > > >> This email is calling for a vote on the release, which will last at
> > > least
> > > >> 72 hours, from Friday, January 30, 2026 at 12:00 pm UTC
> > > >> until Wednesday, February 04, 2026 at 09:00 am UTC
> > > >> <
> > > >>
> > >
> >
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=8&iso=20260204T0900&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/61255
> > > >>
> > > >> Consider this my +1 binding vote.
> > > >>
> > > >> Airflow 3.1.7rc1 is available at:
> > > >> https://dist.apache.org/repos/dist/dev/airflow/3.1.7rc1/
> > > >>
> > > >> "apache-airflow" Meta package:
> > > >> - *apache-airflow-3.1.7-source.tar.gz* is a source release that
> comes
> > > with
> > > >> INSTALL instructions.
> > > >> - *apache-airflow-3.1.7.tar.gz* is the binary Python "sdist"
> release.
> > > >> - *apache_airflow-3.1.7-py3-none-any.whl* is the binary Python wheel
> > > >> "binary" release.
> > > >>
> > > >> "apache-airflow-core" package:
> > > >> - *apache_airflow_core-3.1.7.tar.gz* is the binary Python "sdist"
> > > release.
> > > >> - *apache_airflow_core-3.1.7-py3-none-any.whl* is the binary Python
> > > wheel
> > > >> "binary" release.
> > > >>
> > > >> Task SDK 1.1.7 is available at:
> > > >> https://dist.apache.org/repos/dist/dev/airflow/task-sdk/1.1.7rc1/
> > > >>
> > > >> "apache-airflow-task-sdk" package:
> > > >> - *apache_airflow_task_sdk-1.1.7.tar.gz* is the binary Python
> "sdist"
> > > >> release.
> > > >> - *apache_airflow_task_sdk-1.1.7-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.7 for Airflow package and 1.1.7 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.7
> > > >>
> > > >> Release Notes:
> > > >> - https://github.com/apache/airflow/blob/3.1.7rc1/RELEASE_NOTES.rst
> > > >> -
> > > >>
> > > >>
> > >
> >
> https://airflow.staged.apache.org/docs/apache-airflow/3.1.7/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.7rc1 \
> > > >>    apache-airflow-core==3.1.7rc1 \
> > > >>    apache-airflow-task-sdk==1.1.7rc1
> > > >>
> > > >> Constraints files are at
> > > >> https://github.com/apache/airflow/tree/constraints-3.1.7rc1
> > > >>
> > > >> Cheers,
> > > >> Ephraim
> > > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
> >
>

Reply via email to