I think in code, this might be somewhat already addressed by some plugins being blocked on older versions, etc. but one thing I feel that is sort of missing is a visual and/or code based representation/approval/certification of a plugin being compatible with a given NEW version of unraid.

This is one of my concerns when jumping up new versions, especially when there are significant changes.... will my existing plugins be compatible with the new version.

Because of this, I always generally wait a while once a new version is released to give a chance for plugin updates to be released to correct any issues relating to the new version.

It'd be really good to see some sort of exposure in the web gui of which plugins are confirmed compatible with what versions of unraid.

e.g. If I'm sitting (as I am) on 6.12.15, which of my plugins have since had updates that confirm they're compatible/ok with say, 7.0, 7.1, 7.2? without needing to 'upgrade and find out'. Generally I suppose one can assume compatibility if the plugin has been updated after a given release. But it's not necessarily clear if the plugin developer has actively made changes during a beta or rc period to pre-confirm/test/align/correct compatibility. It'd be nice to have some way of that being able too be flagged/displayed to users in the plugin web interface.

For example I'm sitting on 6.12.15, and I have four plugins that have not been updated during 2025... I don't really know, without spending a lot of time on the forums, if they're properly compatible with 7.0, 7.1, 7.2.

For point of illustration those plugins are:

CA Cleanup App Data, dated 2024.11.28

Dynamix System Temperature, dated 2024.07.10 

SNMP 2023.04.20, but newer one blocked 2024.11.01

ZFS Master dated 2024.12.09.104 

The rest have been updated during 2025, so I can sort of assume/guess that they're compatible with 7.0 and highly likely 7.1... but then 7.2, not sure. Especially since the GUI changes coming in there.

It'd be nice, for example, even with those older ones, even if they don't need an update, for there to be some sort of visual representation that they're confirmed functional and working with current stable versions... before upgrading.

The plugins themselves can have a min value in the entity list that indicate the minimum version they are compatible with. I'm not certain if max is also valid but I image it is. The only real issue I see with this comes down to process. As far as I am aware, it's up to the plugin developers to maintain compatibility and typically, the practice is to note when something isn't compatible, not when something is compatible. Someone correct me if I am wrong. It's easy enough to have some sort of visual indicator that indicates the min version a plugin is compatible with, but that doesn't really indicate compatibility with a new or upcoming version.

TLDR: If you're just talking about taking the part that you mentioned that is already addressed in the code, essentially making that min/max version property visible to the user, I think that would be fairly simple. But if it's a representation/approval/certification of a plugin being compatible with a given NEW version of unraid, that's more of a matter of process than code. That's my take on it anyway.

Not necessarily that formal/certified. More so a visible flag or tickbox for a plugin author to basically flag that the current version is (to the best of their knowledge) compatible with a given release.

e.g. those plugins I've listed, it'd be nice, even without an actual version update, for the author (or maybe the community even) to be able to flag up front that those plugins do indeed work with the latest versions (or not).

Right now the only way one can figure that out is to scour the forums for folks having problems, then assume lack of problems means it works.