WordPress 6 4 will break your Pinegrow blocks

WordPress 6.4 will break Pinegrow blocks in the WordPress Block Editor unless you take action. Check out the links below to the article on Pinegrow's website and the actions you need to take.
🧰 Resources:
• pinegrow.com/blog/how-to-prev... -- Pinegrow tech note with information and compatibility plugin link
• github.com/Pinegrow/LoadLodas... -- Compatibility plugin download page
• github.com/WordPress/gutenber... -- WordPress pull request with issue description and notes
• lodash.com/ -- Lodash information
📝Note: I'm not affiliated with Pinegrow in any way. I'm just a happy, paying customer who wants to see the product continue to grow and thrive, and to help build a more active community around it.

[@tobyfoote]

I'm glad to see this information come out BEFORE the new version on November 7. Great job, as always, posting this information for Pinegrow users.

[@vigilantezack]

Seems like this would effect pretty much every custom block in the history of ever, assuming they used Lodash.
Really wish WP would just create a deprecation setting or something and let people disable it only on new projects. Rather than make us run out to find plugins and tricks to get around it. Now I can see people running "adds lodash" plugins for the next 8 years like people are still running classic editor plugins or jquery plugins.

[@AdamLoweIO]

You are absolutely right. The funny thing is that they expect us to handle block deprecation, but they can't seem to be bothered to do it in their own core code. A lot of block developers are going to be in for a big surprise on Nov 7th.
And yes, I also found myself thinking that this feels a lot like the Jquery Migrate garbage that we still see everywhere.