Given the version string azure-core>=1.0.0b1,<2.0.0 in both a library's setup.py and the repo's shared_requirements.txt, analyze_deps will consider the library's version not to match the frozen version, evidently due to the sorted order of the specifiers:
'azure-core<2.0.0,>=1.0.0b1' which does not match the frozen requirement 'azure-core>=1.0.0b1,<2.0.0'
See e.g. this build.
According to its documentation, specifier order isn't meaningful for setuptools, i.e. <2.0.0,>=1.0.0b1 and >=1.0.0b1,<2.0.0 are equivalent.
Given the version string
azure-core>=1.0.0b1,<2.0.0in both a library's setup.py and the repo's shared_requirements.txt, analyze_deps will consider the library's version not to match the frozen version, evidently due to the sorted order of the specifiers:See e.g. this build.
According to its documentation, specifier order isn't meaningful for setuptools, i.e.
<2.0.0,>=1.0.0b1and>=1.0.0b1,<2.0.0are equivalent.