After you created an plugin that works with the latest released version of GroIMP, you can publish this plugin to the GroIMP plugin manger.

To understand the following steps lets have a look at the plugin infrastructure and the pipeline and what is suppose to happen after a new version (tag) of a plugin is pushed to gitlab.

The infrastructure inside each plugin repository (that has at least one released version) consists of four main components: -

1. The code it self(in git)
2. Ordered List ItemThe package registry (e.g. https://gitlab.com/grogra/groimp-plugins/QSM/-/packages) where the jars and poms of all already released versions are stored. This registry is used for the plugin manager to download the jars and for maven to provide the packages compilation.
3. A gitlab page with the compiled embedded documentation (e.g. grogra.gitlab.io/groimp-plugins/QSM/) this is manly used for the manual web explorer(https://gitlab.com/grogra/groimp-utils/manual-web-explorer) to create https://manual.grogra.de/. This is done so the embedded documentation can be found via search engine or AI bot. Dont be surprise about the question marks on the gitlab page that is only happening there and not on the real website.
4. The plugin.json file (e.g. https://grogra.gitlab.io/groimp-plugins/QSM/plugin.json)