potiuk opened a new pull request #17023: URL: https://github.com/apache/airflow/pull/17023
In case we have additional dependencies between providers released at the same time (for example we need to release sftp and ssh packages now where sftp package depends on release of ssh at the same time) we have to add suffix to the version of the additional_dependency. PIP does not take into account unfortunately that development dependencies should likely be considered as fulfilling the requirement of >=. For example if you have: sftp depends on ssh>=2.1.0 and you release ssh 2.1.0.dev0 at the same time the ssh>=2.1.0 condition is not fulfilled. Same case will be with rc1. Therefore we need to add the suffix in such cross-provider dependencies to be able to install them in CI and in rc candidates. In the future we might ask PIP to change behaviour in such case. <!-- 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 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 change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+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 [UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md). -- 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]
