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
There are 3 yarn scripts that can be run to do the release
48
48
49
49
##### yarn release-beta
50
50
51
-
Automatically calculates and presents 3 beta versions - patch, minor and major for you to choose ( or Other for manual input).
51
+
Automatically calculates and presents 3 beta versions - patch, minor and major for you to choose ( or Other for manual input).
52
52
53
53
```
54
-
? Select increment (next version):
55
-
❯ prepatch (0.1.1-beta.0)
56
-
preminor (0.2.0-beta.0)
57
-
premajor (1.0.0-beta.0)
58
-
Other, please specify...
54
+
? Select increment (next version):
55
+
❯ prepatch (0.1.1-beta.0)
56
+
preminor (0.2.0-beta.0)
57
+
premajor (1.0.0-beta.0)
58
+
Other, please specify...
59
59
```
60
60
61
61
##### yarn release-major-beta
62
62
63
63
Same as `yarn release-beta`, but with premajor version pre-selected.
64
-
64
+
65
65
##### yarn release
66
66
67
67
Generic command, does not automatically add the `beta` to version, but you can still manually write it if you choose Other.
68
68
69
69
#### Important notes
70
70
71
-
> Do not use release-it tool on master branch, the commit on CHANGELOG.md file and the version increase in the package.json file can't be done without a PULL REQUEST.
71
+
> Do not use release-it tool on master branch, the commit on CHANGELOG.md file and the version increase in the package.json file can't be done without a PULL REQUEST.
72
72
73
73
> Do not keep Pull Requests from develop to master branches open when you are doing beta releases from the develop branch. As long as a PR to master is open, an automatic script will run on every commit and will update both the version and the changelog to a production-ready state - ( MAJOR.MINOR.PATCH mandatory format for version).
0 commit comments