-
Couldn't load subscription status.
- Fork 2
Description
Motivation
Currently we build and release the react-native SDK manually from our local machines when it's time for a new release. In order to follow a proper release structure and make the releases visible in the Github repository, we should use the Github release functionality.
This would also improve the SonarQube analysis since it can detect and calculate new issues since the last release making it easier for us to identify issues that were introduced since the last release.
Solution
Automate the release via Github Actions. In Github we can create a new release with a v-prefixed SemVer, e.g. v2.0.0. This should trigger a release pipeline:
- replace the
package.jsonversion number with the release version number (e.g.2.0.0) (similar to how we do this in https://github.com/formbricks/formbricks ) - build the SDK
- release the SDK on npm
Metadata
Metadata
Assignees
Labels
No labels