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: README.md
+11-22Lines changed: 11 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,28 +66,17 @@ Gypcrete does not publish develop builds to the `dist` branch anymore. It now pu
66
66
* When pushed to `develop` branch --> publish a canary build
67
67
* When pushed to `master` branch --> publish a relase build
68
68
69
-
### Releasing
70
-
71
-
We're relying on Lerna for versioning and publishing. When you create a Release on Github, it will trigger task on Travis CI to publish with Lerna. It also converts the lightweight tag created by Github Release to an annotated tag for Lerna to calculate versions.
72
-
73
-
When releasing a new version for Gypcrete, follow the steps:
74
-
75
-
1. Create a release branch `release/x.y.z`
76
-
2.*(Optional)* Release beta builds with `yarn release:pre` locally to specify version.
77
-
3. Bump version for `package.json` and `CHANGELOG`.
78
-
4. Bump children packages version with script:
79
-
```sh
80
-
yarn bumpversion
81
-
```
82
-
This will run `lerna version`, which updates all `package.json` files in `packages/`.
83
-
84
-
5. Commit above changes, then create a pull request for this release branch.
85
-
6.*[Important]* Create a new Release on Github in format of `v3.4.5` once it's merged into `master`.
86
-
Please be sure to prefix the tag name with `v` as Lerna uses them to calculate changes.
87
-
88
-
7. Backport changes from `master` back to `develop` by creating a `backport/x.y.y` branch and create a pull request for that.
89
-
90
-
At the time Github Release is created, it should trigger `yarn release` on Travis CI and publishes packages to npm.
0 commit comments