@falkTX I really love the awesome work you are doing, and I really appreciate the presence of this forum post, but as the size of the community and the number of plugins scale to bigger numbers, won't this result in you becoming a bottleneck for announcing updates? What if someone else releases an update to a plugin? Maybe I'm missing something, but I think it would make more sense if it was possible for each plugin to independently announce updates and corresponding changelogs, rather than aggregate them across all plugins into a single location for announcement.
In fact, this is exactly how Google Play Store handles it, so you could take a leaf out of their book here. When you visit any app in the Play Store, it displays a "What's New" section so you can see what recently changed. That's a good start, it's still annoyingly vague and incomplete, because it's never clear exactly what changed or when or for which version. So moddevices could do better than google. Ideally it would break down the changes per release, specifying a) the version number of the new release, b) the date of release, and c) what changed. This is exactly what git supports natively via tags, and this is already taken advantage of by sites such as GitHub:
So why not do the same for plugins?
Going one step further, it would be awesome if plugins could adhere to Semantic Versioning, so that plugin consumers can make an educated decision about when it's safe to update.