If they have not released a fixed version by the time we are about to release Scrapy 2.1, we can change our documentation requirements temporarily to specify a Sphinx version older than 3, since we are not using anything specific of Sphinx 3 at the moment.
@anusha94 Given the circumstances, I think it makes sense for us to handle this from the core team.
Hi! I'm one of the authors of sphinx-hoverxref. I've already released 0.2b that includes the fix for Sphinx 3.0. I took a look at the PR and saw that the new warnings made your build to fail (I'm sorry for that), and I created a new issue to take a deeper look at this at readthedocs/sphinx-hoverxref#58