I think yes - if it appeared in 3.0.3 and was not there before, this is a very basic behaviour that users might rely on - so I'd also be for rc4 - possibly with accelerated vote.
J. On Sat, Jul 5, 2025 at 9:32 PM Jens Scheffler <j_scheff...@gmx.de.invalid> wrote: > airflow-core: +1 (binding) - Checked SVN, Reproducible package build, > Licenses, Signatures > > Interestingly it showed the file apache-airflow-3.0.3-source.tar.gz be > binary different but when un-packing the content is the same. I assume > order or metadata of compressed content is different but if expanded > content is the same then I think this is OK. > > task-sdk: +1 (binding) - Checked SVN, Reproducible package build, > Licenses, Signatures > > Tested 3.0.3rc3 with EdgeExecutor and one INtegration Test Dag - all > looks OK. Except the Grid display refresh problem that Jarek mentioned. > I would prefer having this fixed because as a User I'd expect that such > basic problem is not added as regression in a patch release. But no > strong opinion though. In 2.10 there always was a togle to turn > auto-refresh on again as it turns off when no Dag run is active, in the > new UI we do this all automatically and the only option is to use F5 or > navigate out- and back-in if Dag runs were inactive before and you start > a new one. > > Jens > > On 05.07.25 15:24, Jarek Potiuk wrote: > > * airflow-core, airflow: +1 (binding): checked reproducibility, > > licences, signatures, checksums. > > * task-sdk: +1 (binding): checked reproducibility, licences, > > signatures, checksums. > > > > I also ran a few Dags and clicked through the UI and I found one issue > > which I am not sure if it is a regression or not. When you trigger a > > dag from dag view, the screen does not refresh after trigger and you > > need to manually refresh it to see the new run appear in the grid. The > > status of tasks refreshes automatically then - but you need to at > > least once click "refresh" to get the grid show the new dag run. You > > can see it happening in this recording: > > > https://drive.google.com/file/d/1VbQ_464jWPFwxIyM5FC44kTP6q-2L6oo/view?usp=drive_link. > > > I created an issue for it https://github.com/apache/airflow/issues/52907 > > > > I also found one issue with reproducibility of "airflow-core" -> when > > I generated the packages (both whl and sdist) I have an additional > > "openapi-merged.json" file - but this is not blocking the release and > > I think for the future we should just exclude it from the generated > > package, I will add a fix for that. > > > > Screenshot 2025-07-05 at 14.43.41.png > > > > J. > > > > On Fri, Jul 4, 2025 at 3:32 PM Kaxil Naik <kaxiln...@gmail.com> wrote: > > > > Hey fellow Airflowers, > > > > The release candidates for A*pache Airflow 3.0.3rc3 *and *Task SDK > > 1.0.3rc3* are > > now available for testing! > > > > This email is calling for a vote on the release, which will last > > at least > > until 8th July and until 3 binding +1 votes have been received. > > > > Consider this my +1 binding vote. > > > > Airflow 3.0.3rc3 is available at: > > https://dist.apache.org/repos/dist/dev/airflow/3.0.3rc3/ > > > > "apache-airflow" Meta package: > > > > - *apache-airflow-3.0.3-source.tar.gz* is a source release that > > comes > > with INSTALL instructions. > > - *apache-airflow-3.0.3.tar.gz* is the binary Python "sdist" > > release. > > - *apache_airflow-3.0.3-py3-none-any.whl* is the binary Python > > wheel > > "binary" release. > > > > > > "apache-airflow-core" package > > > > - *apache_airflow_core-3.0.3.tar.gz* is the binary Python "sdist" > > release. > > - *apache_airflow_3.0.3-py3-none-any.whl* is the binary Python > > wheel > > "binary" release. > > > > > > Task SDK 1.0.3rc3 is available at: > > https://dist.apache.org/repos/dist/dev/airflow/task-sdk/1.0.3rc3/ > > > > "apache-airflow-task-sdk" package > > > > - *apache_airflow_task_sdk-1.0.3.tar.gz* is the binary Python > > "sdist" > > release. > > - *apache_airflow_task_sdk-1.0.3-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.0.3 for Airflow package and 1.0.3 for Task SDK. This will > > allow us > > to rename the artifact without modifying > > the artifact checksums when we actually release. > > > > --- > > > > Changes since rc2: > > > > - Run trigger expansion logic only when ``start_from_trigger`` > > is True > > (#52873) > > > > *Docs* (for preview): > > https://airflow.staged.apache.org/docs/apache-airflow/3.0.3 > > *Release Notes*: > > > > - https://github.com/apache/airflow/blob/3.0.3rc3/RELEASE_NOTES.rst > > - > > > https://airflow.staged.apache.org/docs/apache-airflow/3.0.3/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.0.3rc3 --pre > > ``` > > > > Constraints files are at > > https://github.com/apache/airflow/tree/constraints-3.0.3rc3 > > > > Regards, > > Kaxil > > >
