community-plugins support for maximum version

When building a python plugin that loads/installs a native plugin, it would be great if there was support for maximum version. This would, for example, make it obvious before installing a plugin that it wasn't compatible with dev.

Mar 31 '23 19:03 psifertex

We should also add support for a full semver comparison instead of just the build.

Oct 30 '23 20:10 psifertex

Additionally, it would be a nice addition if we could go ahead and say that a plugin is only compatible with a certain branch or set of branches in addition to the version constraints.

Jan 31 '24 19:01 ExecuteProtect

Closing this here as we're tracking this as a part of our migration to the new extension manager and updated plugin manager format which supports a maximum version.

Oct 15 '24 18:10 psifertex

Closing this here as we're tracking this as a part of our migration to the new extension manager and updated plugin manager

@psifertex Is there another public issue for that that you can link to to maintain context/continuity? And/or a potential timeline?

Oct 15 '24 23:10 0xdevalias

It's technically already supported but only for official plugins. At this point keep an eye out on the blog which is where we'll be releasing information on the new system when it's available. I expect it in the "G" release.

Oct 15 '24 23:10 psifertex

@psifertex Cool, thanks for the info :)

Oct 15 '24 23:10 0xdevalias