Release packages with CI

[boeckMt]

Right now we had a lot ideas, how to automatically create npm packages on certain events.

• Fix release of npm packages #81
• Main Release was not triggered after pull request #79
• Update Github Workflows to create prereleases #65
• Prereleases Versions on NPM #62
• Publish packages to Npm #31

Nothing is like it should be...

The problem is, we would like to easily publish new packages after some specific pull requests.
The versioning for that should follow the semver versions, and the release should be updated in our CHANGELOG.md like described in #62

But it shouldn't be possible to accidentally publish new Versions which are not reviewed by a pull request, except for pre release versions.

[boeckMt]

The Current workflow described in publish-a-new-version works kind of but, it is possible to create a main version tag on the master, and push it so the pull request is bypassed, which should not be possible for main version tags.

[boeckMt]

Do we need running the Test and Build CI workflow also for main releases?

Normally this workflow should have passed bevor on merging the last state into the master so we can skip this.

• https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore
• https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet

# e.g.
on:
  push:
    branches-ignore:
      # run on all branches other then main and release
      - main
      - release-v[0-9].[0-9]+.[0-9]+

[boeckMt]

Check to use deployment with

• Conventional Commits
• Conventional Changelog