potiuk edited a comment on pull request #18228: URL: https://github.com/apache/airflow/pull/18228#issuecomment-920724218
> Yay my guess is correct. The dev version was pulled because previously we had moto~=2.2, >=2.2.1.dev9. According to PEP 440, if the version range specifier contains a prerelease, prereleases will be considered when pulling in dependencies, which is why a dev version was pulled with --upgrade-strategy=eager. TIL! So it was close guess. boto and moto - only one letter different ;). I will add a feature to show diff vs. "fixed" constraints whenever we get a failure on "eager upgrade" build and make it quite prominent with some description like. --------------------- If you see an unexpected test failures here, it might be because of upgraded dependencies (this build was run with eager upgrade on dependencies due to changed setup.* files) Please check if the test also fails in `main` branch and if so, it's likely that the reason is one of those: <DIFF HERE> --------------------- -- 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]
