+1 (binding), checked: - SVN - in Docker installation - Reproducible package builds - Licence - Signature - Checksums
Thanks! Best regards, Wei Lee On 2026/09/25 08:22:48 Pankaj Koti via dev wrote: > +1 non-binding > > Tested that my PRs are included in the RC and working as expected, thanks > for cutting the release! > > On Fri, Sep 25, 2026 at 3:32 AM Jarek Potiuk <[email protected]> wrote: > > > +1 (binding) > > > > Checked: > > > > * SVN: all expected files present (check-release-files), and all 78 RC > > providers install at their RC versions (Dockerfile.pmc) > > * Signatures: all 157 good (Shahar's key from KEYS) > > * Checksums: all 157 SHA512 good > > * Licences: Apache RAT 0.18 - 0 unapproved, 0 unknown > > * Reproducible builds: the source tarball and all 156 packages are > > byte-identical when rebuilt from the providers/2026-09-22 tag with > > flit 4.0.2 > > > > One note on reproducibility, not a blocker: the wheels were built with > > flit 4.0.2, but dev/breeze/uv.lock at the tag locks flit 4.1.0. Since > > flit builds without isolation, rebuilding with the locked Breeze (as > > the docs say) gives 75 wheels that differ only in the "Generator:" > > line of their WHEEL file (and its hash in RECORD) - the packaged files > > are identical. I opened a PR explaining how to rebuild with the > > release manager's flit version: > > https://github.com/apache/airflow/pull/73699 > > > > I also tested all my changes in this wave with all 78 RC providers > > installed from the PyPI wheels in Breeze (Airflow 3.3.2): > > > > * #72162 (amazon, google, microsoft.azure) - remote log uploads outside > > base_log_folder are skipped, uploads inside still work > > * #72166 (google) - Drive q= values are escaped > > * #73413 (common.sql) - DataFusion error message shows the storage type > > * #72627 (edge3) - docs only, present in the release > > * #72174 (snowflake) and #72176 (teradata) - in the wave, though not > > listed in the testing issue - both work as expected > > > > Improvement to the verification process: > > > > I tested all my changes with an agent using Apache Magpie's > > release-management > > "verify-rc" skill and a new Airflow override that adds an optional "test > > your own changes" step. The agent found my entries in the testing issue > > (and the two changes missing from it), verified each change is in the > > RC tags, changelogs and wheels, downloaded the whole wave and wrote a > > Dag exercising every change - I only had to start Breeze and trigger it. > > It also ran the regular checks above and tracked down the flit > > difference. > > > > That was a very good experience - I highly recommend trying it: > > https://github.com/apache/airflow/pull/73697 > > > > J. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
