build: fix release automation

[petermetz]

Adds a GitHub workflow yaml file that executes the
publish script.
This workflow only gets triggered when a git tag has been
created that starts with the letter v (as in version).

Fixes #1951
Fixes #2054
Fixes #2175

Signed-off-by: Peter Somogyvari [email protected]

[takeutak]

@petermetz I appproved this pull-request, but let me confirm your intention.
In my understanding, your changes mean that you want to execute the workflow only if the version tag (e.g. "v1.1.0") is created (to reduce the work of CI), is it right?

[petermetz]

@petermetz I appproved this pull-request, but let me confirm your intention. In my understanding, your changes mean that you want to execute the workflow only if the version tag (e.g. "v1.1.0") is created (to reduce the work of CI), is it right?

@takeutak Thank you for the review! Yes, this is correct all correct. In addition to reducing load on the CI we also have to limit auto-publishing packages this way (instead of auto-publishing for each pull-request & commit on the main branch) because there are limits on how many versions packages can have both on npm and on the github package manager. I don't remember the exact numbers but back when I read up on the limits they were around a thousand versions per package meaning that if I let the CI auto-publish on every commit of the main branch then we'd hit the version limit and would have to start deleting older versions of the package manually as we add new commits to main. So the middle ground I choose is that we can manually control when we auto-publish based on tagging commits on the main branch.

[petermetz]

Well, it did not work out the way I thought it would so now here's the follow-up: #2186