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
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,17 @@ yarn lint
54
54
55
55
## Releasing alpha versions
56
56
57
-
1. Add a branch which will be releasing alpha version to .azure-devops\graphitation-release.yml into `trigger`
58
-
2. Change `release` script in the root package json to `yarn beachball publish -t alpha`,
59
-
3. Modify package.json of the package you want to release to x.x.x-alpha.0
60
-
4. Every time you want to release a new version use `yarn change` and select `prelease`. To avoid patching of dependent packages set `dependentChangeType` to `none` manually in .changes directory
57
+
Generraly you need to only run pipeline [microsoft.graphitation](https://dev.azure.com/DomoreexpGithub/Github_Pipelines/_build?definitionId=8) and that is all.
58
+
59
+
Here described detailed steps of the release process:
60
+
61
+
1. Make sure you have generated change files for your changes using `yarn change` command.
62
+
1. In Azure DevOps run pipeline [microsoft.graphitation](https://dev.azure.com/DomoreexpGithub/Github_Pipelines/_build?definitionId=8)
63
+
1. Pipeline automatically adds the `alpha` tag and prefix to the version.
64
+
1. The package will be published to npm with the `alpha` tag, so you can install it using `npm i @graphitation/PACKAGE@VERSION-alpha.XX`
65
+
1. Bot push the bump commit to the branch.
66
+
67
+
The core logic is `-b "$releaseBranch" -t alpha --prerelease-prefix alpha` flags for beachball publish command which are added in the [graphitation-release.yml](.azure-devops/graphitation-release.yml#L66) pipeline.
0 commit comments