coinstatsindex was updated in an incompatible way in v30 (see #30469) and moved to the indexes/coinstatsindex folder. The old indexes/coinstats directory was kept and a warning was logged so users could still downgrade to v29 without resyncing the index.
There was a TODO in the code that scheduled the deletion for v31. Since v32 branch-off has happened, this would now ship in v33. By then 29.x should be EOL assuming we are not going to release a v29.5.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline and AI policy for information on the review process.
If your review is incorrectly listed, please copy-paste <code><!--meta-tag:bot-skip--></code> into the comment that the bot should ignore.
<!--174a7506f384e20aa4161008e828411d-->
No conflicts as of last run.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
Concept ACK
ACK 82e4cc6964a9a130d3a41454e046af964ea05508
Shouldn't deletion of the old one be done after the creation of the new one that potentially did not yet occur? The new one shouldn't need to have the old one to be created, but that 'feels' risky?
Shouldn't deletion of the old one be done after the creation of the new one that potentially did not yet occur? The new one shouldn't need to have the old one to be created, but that 'feels' risky?
This isn't a concern. The new index doesn't use the old version at all. It is incompatible and has been synced from scratch since v30, so the old data is never read from there and so the order doesn't matter.
Rebased
Milestone
33.0