Hi @alexzlobin thanks for sharing this - we would always recommend with any release that it’s thoroughly tested in a staging/dev environment, including migrating your existing data, so your recommendations align with that. You’ll almost always need to get a third party plugin updated when a new minor or major release comes out, especially one which does as much as this release does to improve the code base ‘under the hood’.
Regarding the specific points that are not very specific, so I can’t tell you if they’re for sure fixed yet, you might want to check the PRs merged already for the upcoming 7.2.1 release - in particular there was something that was missed as a deprecation which affected plugins and which was addressed super quickly with a fix already merged:
It helps if you can actually raise these issues, so that the core team can be made aware of and investigate them. Please search forums/GitHub first, and if you have experienced something that isn’t reported, please flag it up and we’ll get right on it. This is the best way to get such bugs fixed.