[Feature Request] Some way to distinguish stable vs dev versions

[FallenCharlotte]

For example in PropEdit, versions up to v0.2.1 only work in stable, whereas the newer versions only work in dev.

Not sure if this could work in the manifest file, but one possibility is for dev-only versions to be marked as pre-release on Github.

[LightAi39]

The plugin only checks the release tagged as latest, and I don't know how a GitHub release could include information about the compatibility of stable/dev in a clean way, as using pre-releases is kinda misusing the real use of pre-releases, which could become a problem for any project using them in the intended way.

And I guess technically the plugin is still out of date if newer versions exist that only work on dev, so I don't know if it matters that much in practice. If you include a warning about dev branch being required in the release it would inform the user to make their own decision between updating or not updating CM to dev branch.

The warning in the editor isn't intrusive and includes the tag name of the newer release, so it could easily be ignored when a user knows it's not a problem for them.

I also think the general consensus is that dev branch is pretty much better to use right now anyway, with all the V3 support missing from stable. And most of these incompatibility issues will likely be gone when V3 changes get pushed to stable, so it's likely to be only a temporary issue. So unless there is a good long-term solution I am missing I think it's a bit messy to try and throw something together for now.

But if you know of a good way to do this, I'd be open to implementing it, I just have no idea how to do it cleanly right now.