Auto-publish new versions to NPM
Problem
Currently, to deploy a new version of the JS SDK a developer needs to run yarn lerna:publish
locally and have the correct access rights. This process is error prone and depends on specific people with the correct access rights
Desired Outcome
Publishing a new version of the SDK should be done via a Gitlab pipeline.
Open for discussion
- How should the pipeline be triggered, potential solutions:
- manually
- on merge of a new version number
- By creating a separate release branch with a specific version number
An exploration into how other open-source SDKs handle this is probably helpful here.
Edited by Sebastian Rehm