WooCommerce – plugins of unknown compatibility – please let them know?

Situation;
Recent versions of WooCommerce have required that woocommerce plugins declare that they are compatible. This declaration is made by setting some tags in the plugin header.

I have endeavored to inform plugin authors that their plugins were being reported as “unknown compatibility” by WooCommerce.
Some made appropriate updates, some did not.
Of those that did not, I was unable to further draw their attention to this, having already started the topic. So for them I wrote a review each, that also attempted to draw their attention to this requirement by WooCommerce.

It is a good prudent approach to make sure that plugins are compatible, one that would have been great to have right from the start.

Problem;
The introduction of the required header tags, has clearly not been noticed by many plugin authors.

Solution Suggestion;
Could you (the WooCommerce Team) please carry out a second attempt to make sure that all WooCommerce plugin authors are aware (so they know) of these new requirements, and how to satisfy the requirements?

Further Appreciation
1) Plugin Author’s
Some plugins may well be compatible, and work very well. But they get reported as “Unknown Compatibility” because they have not satisfied these new requirements. Good or excellent as the coding may be, it doesn’t look so good for their expertise.

2) WooCommerce Users
When faced with a plugin that is reported as “Unknown Compatibility” a user can do any of the following;
a) update WooCommerce anyway, and “hope” all goes well.
b) contact the Plugin Author team, and accept their re-assurance that the plugin is compatible, even though they still do not put out an update that openly declares it to be compatible.
c) contact the Plugin Author team, and get no result and update WooCommerce anyway, and “hope” all goes well.
d) contact the Plugin Author team, and try to effect a result, that satisfies the new requirements.
e) dump plugins which are no-longer compatible
f) dump WooCommerce and look for other systems and platforms that satisfy the needs that had previously been met.
g) wait
h) contact WooCommerce – the upstream cause of these reports, and try to get the problem sorted out.

It would be a fairly sure bet that a significant number of users are choosing some of these options which may not be secure, or not a prudent habit to get into, especially in this case of WooCommerce being their transactional functions in a business.
User may be being conditioned to accept less secure relationships between WooCommerce and its Plugins than should be able to be expected, in the interests of remaining in an operational and apparently up to date configuration.

This particular user prefers a higher level of integrity in the certainty of interconnectedness between the related Plugins, and imagines that WooCommerce would be inclined to have similar leanings.

So please, if you can, bolster the resilience of the WooCommerce community of plugins, and do what it takes for all the plugin author teams to become cognizant of these new requirements.

Thank you very much, in anticipation of a full restoration of operational capacity.