#26201 removed taproot from getdeploymentinfo (not yet in a release, slated for v32), which it turns out Lnd relies on: https://github.com/lightningnetwork/lnd/pull/10683
Expand the release doc note to recommend the same solution they used: check for TAPROOT in the script_flags array. This was added in v31.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process. A summary of reviews will appear here.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
We only added the script_flags array in v31.0, so it may be a bit annoying for RPC clients to have to use getdeploymentinfo for v30 and older. Since #26201 isn't in a release yet, we could temporarily put "taproot" back under deployments with a deprecation notice. Perhaps that's useful if Lnd is not the only client with this issue (since they've already dealt with it).