potiuk commented on PR #33822: URL: https://github.com/apache/airflow/pull/33822#issuecomment-1697308505
This is because your PR generally changes dependencies and it means that it triggers eager upgrade - which means that we had to resolve and find new set of dependencies that your new dependencies and Airflow in general sees as consistent set of dependencies. Generally follow the advice and attempt to fix it:  The thing is that another dependency that is being upgraded adds extra information or changes the definition of the other thing that causes mypy to see it as an issue. The best way to fix it is to figure out how to fix it and submit a separate PR to fix it and then rebase your PR. Or you can wait until someone else fixes it. This what happens now with main builds (canary builds) - see here: https://github.com/apache/airflow/actions/runs/6011017073/job/16304198261 Whoever fixes it - fixes it for the other as well. The fastest way to deal with it is to fix it yourself. -- 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]
