-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump minimum version for azure containerinstance. #40767
Bump minimum version for azure containerinstance. #40767
Conversation
The apache#40616 used priority for ContainerGroup and it has only been added in 10.1.0 version of azure-containerinstance library See https://pypi.org/project/azure-mgmt-containerinstance/10.1.0/
Detected by canary builds. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
interesting. I thought we are checking also against min versions of the depended libs?
Generally speaking if we would know this during review of the PR I would be favor in adding a check for supported version of the lib
Yes.I am trying to see if we can do it on all PRs in a selective way here: #40768 - becaue currently "special" tests are not run on most of regular PR (which is good), but the "lowest dependency" tests should also run there, I think in all PRs (though they are considerably slower than regular tests so there is a trade-off). |
Previously lowest-dependency tests were only run as part of "special" tests - which means that they were not run on regular PRs which did not touch dependencies. But those tests should also be run on regular PRs even if the PR does not change dependencies - because just using a new feature might cause lowest dependencies to fail (Similarly as in apache#40767
Yep #40768 should fix it - I was afraid we will hit the workflow limit when I separate it out, but seems that we are not, so it's good to go. |
Previously lowest-dependency tests were only run as part of "special" tests - which means that they were not run on regular PRs which did not touch dependencies. But those tests should also be run on regular PRs even if the PR does not change dependencies - because just using a new feature might cause lowest dependencies to fail (Similarly as in #40767
The apache#40616 used priority for ContainerGroup and it has only been added in 10.1.0 version of azure-containerinstance library See https://pypi.org/project/azure-mgmt-containerinstance/10.1.0/
Previously lowest-dependency tests were only run as part of "special" tests - which means that they were not run on regular PRs which did not touch dependencies. But those tests should also be run on regular PRs even if the PR does not change dependencies - because just using a new feature might cause lowest dependencies to fail (Similarly as in apache#40767
The #40616 used priority for ContainerGroup and it has only been added in 10.1.0 version of azure-containerinstance library
See https://pypi.org/project/azure-mgmt-containerinstance/10.1.0/
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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.