github-actions[bot] opened a new pull request, #71149: URL: https://github.com/apache/airflow/pull/71149
* Fix provider distribution builds failing with flit 4 flit 4.0 removed the --setup-py/--no-setup-py options, so every flit-backed provider build now aborts during argument parsing as soon as flit 4 resolves. Not generating setup.py has been flit's default since well before the 3.12 floor breeze requires, so no longer asking for it explicitly leaves the built distributions unchanged. * Cap flit below 4 so provider distributions keep valid metadata `flit build` does not use PEP 517 build isolation, so whichever flit_core is installed becomes the backend for every provider distribution and the `flit_core==3.12.0` pin each provider declares never applies on the path we release from. flit_core 4.0.1 writes Import-Name and Import-Namespace without a trailing newline (https://github.com/pypa/flit/issues/813), consuming the blank line that separates the metadata headers from the description, so the resulting METADATA parses with MissingHeaderBodySeparatorDefect. Removal of the cap is tracked at https://github.com/apache/airflow/issues/71121. * Drop the flit flag regression test The assertion mirrors the argv literal it guards and mocks away the argument parser that actually rejected the flag, so it detects reverts rather than the class of breakage it was written for. The provider distribution build jobs cover that. * Rest the flit cap on the unvalidated backend rather than the 4.0.1 defect flit 4.0.2 fixed the METADATA corruption the comment cited, but the reason to hold the backend at 3.12.0 is that nothing has exercised flit 4 against provider distributions or the reproducible-build checks. --------- (cherry picked from commit 9a85faa9c55b907bd105ee41567bb7d55dab9f31) Co-authored-by: rjgoyln <[email protected]> Co-authored-by: Rahul Vats <[email protected]> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
