potiuk opened a new pull request, #26122: URL: https://github.com/apache/airflow/pull/26122
So far when we attempted to upgrade requirements of a dependency with fixed requirement or when the new range was not overlapping with the old rangem we had to synchronize pushing constraints at the same time as merging the setup.py/setup.cfg change - otherwise regular PR that did not have "--upgrade-to-newer-dependencies" derived, failed because of conflicting constraints. This PR solves the problem by attempting to rebuild the image again - this time with "--upgrade-to-newer-dependencies" set when the first attempt to build fail in CI. The effect of it should be that the image should not fail and let the regular PRs continue, while the constraints are being updated in main. This should finally make the builds self-maintainable even if we bump fixed constraints. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments). -- 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]
