Generate and publish build constraints#68937
Draft
nailo2c wants to merge 2 commits into
Draft
Conversation
Build backends can publish breaking releases independently of Airflow, making isolated sdist builds non-reproducible. A pinned build-time dependency artifact is needed before installation flows can adopt reproducible build isolation safely.
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is PR 1 of the four-PR replacement for #65511.
It generates pinned build constraints from workspace and locked sdist build metadata, uploads them with the existing constraints artifacts, and publishes them to the constraints branch.
The generated
build-constraints-*.txtfiles are inert in this PR. Airflow installation flows do not consume them yet.Validation:
breeze run pytest scripts/tests/in_container/test_generate_build_constraints.py -xvs— 68 passedprek run ruff --from-ref upstream/mainprek run ruff-format --from-ref upstream/mainprek run --from-ref upstream/main --stage pre-commitprek run --from-ref upstream/main --stage manual.txtfiles; nothing was pushedrelated: #54394
Was generative AI tooling used to co-author this PR?
Generated-by: Codex (GPT-5) following the guidelines