It's a tracking issue for issues and PRs that should land in the next v0.12.3 release of esplora-client.
We are planning this v0.12.3 release from the release/0.12.x in order to have the deprecation warning of the methods that are planned to be removed in the next MAJOR release v0.13.0.