[v2-11-test] Fail prod image release when constraint build fails (#62… - #62837
Merged
Conversation
…che#62387) When constraint build fails, building prod and ci image by default fall back to "no-constraints" build in order to account for newly added or modified dependencies that conflict with constraints, however in case of release build, such fallback should not happen - simply the build should fail if constraints are conflicting. This avoids the case that we had with virtualenv being removed from PyPI pypa/virtualenv#3061 (cherry picked from commit 62121a0) Co-authored-by: Jarek Potiuk <jarek@potiuk.com> Closes: apache#62349
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
1 participant
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.
…387)
When constraint build fails, building prod and ci image by default fall back to "no-constraints" build in order to account for newly added or modified dependencies that conflict with constraints, however in case of release build, such fallback should not happen - simply the build should fail if constraints are conflicting.
This avoids the case that we had with virtualenv being removed from PyPI pypa/virtualenv#3061 (cherry picked from commit 62121a0)
Closes: #62349
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.