Overhaul CI/CD Publishing

[SundermannC]

Currently, the CI/CD pipeline tries to publish a new version after every push to the main branch and fails for that.
The publishing step should rather be tied to actual releases and the scripts need to be fixed.

[gravemalte]

I would vote for only triggering the CI publish when we create a v tag. We should remove the publishing when pushing on main.

[SundermannC]

I like your suggestion very much. What do you think @jagalindo and @coemgen1992?

[jagalindo]

I guess this is an old thread, overrided by the new CI. Nonetheless there might be some bad runs created when implemented it. Currently, we cannot commit to main. The CI process we implemented is as follows.

• we commit only to develop (any minnor changes, any feature request). This releases a Snapshot/dev version automatically so all the tools within the ecosystem can adapt to/test them.
• When agreed, we pr to main (3 reviewers are needed to merge) and then the next stable release is created.

In other words, main will always have the code of the latest stable release, while dev, will have the active more changing code