You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+9
Original file line number
Diff line number
Diff line change
@@ -42,3 +42,12 @@ We use GitHub issues to track public bugs. Report a bug by opening a new issue i
42
42
- What you expected would happen
43
43
- What actually happens
44
44
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
45
+
46
+
## Release procedure
47
+
48
+
Each PR to the `main` branch has to pass the `build`, `test`, `lint` and `code coverage` steps from the CI. The PR also needs a review from one authorized person.
49
+
All commits needs to be signed to pass the DCO check.
50
+
51
+
After the PR is merged, a new `next` version is build and deployed to `npmjs` for all packages with the `next` tag.
52
+
53
+
The release of a new version is done by running the `release` workflow manually. This workflow can only be triggered successfully by an authorized person that is listed inside the `CODEOWNERS` file. The test and coverage steps are executed again and the new version is published to `npmjs` for all packages with the `latest` tag. The version number is calculated based on the commits since the last release and the `semver` rules.
0 commit comments