This is another good reason for trimming one's tool set down: makes it easier to keep track of updates. However, even though I've been making a conscious effort to limit my plugins, it's still a challenge and sometimes I go a month or more before accidentally finding out there's an update to one of my less-used items.
I, too, often rely on cclarry for the heads-up. Even when there's a vendor update notification in my in-box I'll still often read about it here first.
What's really needed is a central database, preferably one that the vendors themselves keep up-to-date. KVR would be the logical place to host such a resource. It would contain a list of products, their current version, the date the current version was released,
and a link to the change log.
That last bit's important because not all updates are worth bothering with. Sometimes the only thing that's changed is they've added an AU or AAX version, or fixed a bug that only applies to FL Studio.
Mike, feel free to start that database!