-1 (binding) for Airflow/Airflow-Core: Found an issue in a migration file when 
using SQLite.

fix https://github.com/apache/airflow/pull/63256

Best,
Wei

> On Mar 10, 2026, at 3:39 PM, Ephraim Anierobi <[email protected]> 
> wrote:
> 
> +1 (binding) - (for both) checked svn, reproducible build, licences,
> signatures and checksums
> 
> I also ran a couple of example dags
> 
> On Sat, 7 Mar 2026 at 23:05, 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 test round using EdgeExecutor and Integration Test Dag.
>> 
>> Only found one minor UI glitch, when you had either Rendered Templates
>> or XCom tab in Dag run/Task Details selected and click on a mapped task,
>> then the UI shows an error and further displays the tabs even if this
>> tab view is not available on a mapped task. Did a short check but this
>> UI glitch is also in 3.1.7 so not a regression.
>> 
>> On 07.03.26 15:28, Jarek Potiuk wrote:
>>> +1 (binding) both Airflow/Airflow-Core and TaskSDK
>>> 
>>> Checked (for both)
>>> * SVN
>>> * Reproducibility
>>> * Signatures
>>> * Checksums
>>> 
>>> Checked licences for sources
>>> 
>>> I run Airflow  3.1.8rc1 with some example dags in Breeze, all looks good.
>>> I checked my changes, including testing the updated docker-compose with
>>> updated health-checks, all works out-of-the-box.
>>> 
>>> J.
>>> 
>>> 
>>> 
>>> 
>>> On Fri, Mar 6, 2026 at 9:09 PM Buğra Öztürk <[email protected]>
>> wrote:
>>> 
>>>> +1 (binding) for both Airflow/Airflow Core and TaskSDK releases. I have
>>>> checked,
>>>> Airflow/Airflow Core:
>>>> - SVN
>>>> - Reproducible package builds
>>>> - Licence
>>>> - Signature
>>>> - Checksums
>>>> TaskSDK:
>>>> - SVN
>>>> - Reproducible package builds
>>>> - Licence
>>>> - Signature
>>>> - Checksums
>>>> 
>>>> Best Regards,
>>>> 
>>>> 
>>>> On Fri, Mar 6, 2026 at 12:23 PM Rahul Vats <[email protected]>
>> wrote:
>>>> 
>>>>> Hey fellow Airflowers,
>>>>> 
>>>>> The release candidates for Apache Airflow 3.1.8rc1 and Task SDK
>> 1.1.8rc1
>>>>> are now available for testing!
>>>>> 
>>>>> This email is calling for a vote on the release, which will last at
>> least
>>>>> 72 hours, from Friday, March 06, 2026 at 12:00 pm UTC
>>>>> until Wednesday, March 11, 2026 at 09:00 am UTC
>>>>> <
>>>>> 
>>>>> 
>>>> 
>> https://www.timeanddate.com/worldclock/fixedtime.html?msg=8&iso=20260311T09&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/62987
>>>>> 
>>>>> Consider this my +1 binding vote.
>>>>> 
>>>>> Airflow 3.1.8rc1 is available at:
>>>>> https://dist.apache.org/repos/dist/dev/airflow/3.1.8rc1/
>>>>> 
>>>>> "apache-airflow" Meta package:
>>>>> - *apache-airflow-3.1.8-source.tar.gz* is a source release that comes
>>>> with
>>>>> INSTALL instructions.
>>>>> - *apache-airflow-3.1.8.tar.gz* is the binary Python "sdist" release.
>>>>> - *apache_airflow-3.1.8-py3-none-any.whl* is the binary Python wheel
>>>>> "binary" release.
>>>>> 
>>>>> "apache-airflow-core" package:
>>>>> - *apache_airflow_core-3.1.8.tar.gz* is the binary Python "sdist"
>>>> release.
>>>>> - *apache_airflow_core-3.1.8-py3-none-any.whl* is the binary Python
>> wheel
>>>>> "binary" release.
>>>>> 
>>>>> Task SDK 1.1.8 is available at:
>>>>> https://dist.apache.org/repos/dist/dev/airflow/task-sdk/1.1.8rc1/
>>>>> 
>>>>> "apache-airflow-task-sdk" package:
>>>>> - *apache_airflow_task_sdk-1.1.8.tar.gz* is the binary Python "sdist"
>>>>> release.
>>>>> - *apache_airflow_task_sdk-1.1.8-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.8 for Airflow package and 1.1.8 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.8
>>>>> 
>>>>> Release Notes:
>>>>> - https://github.com/apache/airflow/blob/3.1.8rc1/RELEASE_NOTES.rst
>>>>> -
>>>>> 
>>>>> 
>>>> 
>> https://airflow.staged.apache.org/docs/apache-airflow/3.1.8/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.8rc1 \
>>>>>   apache-airflow-core==3.1.8rc1 \
>>>>>   apache-airflow-task-sdk==1.1.8rc1
>>>>> 
>>>>> Constraints files are at
>>>>> https://github.com/apache/airflow/tree/constraints-3.1.8rc1
>>>>> 
>>>>> 
>>>>> Regards,
>>>>> Rahul Vats
>>>>> 
>>>> 
>>>> --
>>>> Bugra Ozturk
>>>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
>> 

Reply via email to