root / HServer / 00.Server / 00.Program / node_modules / mongoose / release-items.md
이력 | 보기 | 이력해설 | 다운로드 (1.13 KB)
| 1 |
## mongoose release procedure |
|---|---|
| 2 |
|
| 3 |
1. tests must pass |
| 4 |
2. update `package.json` and `package-lock.json` version |
| 5 |
3. update History.md using `git changelog` or similar. Add #<TICKET_NUMBER> as well as a link to the github user who fixed it if applicable. |
| 6 |
4. git commit -a -m 'release x.x.x' |
| 7 |
5. git tag x.x.x |
| 8 |
6. `npm run release`, or `npm run release-legacy` for 4.x |
| 9 |
7. update mongoosejs.com (see "updating the website" below) |
| 10 |
8. tweet changelog link from [@mongoosejs](https://twitter.com/mongoosejs) |
| 11 |
9. Announce on mongoosejsteam slack channel |
| 12 |
10. change package.json version to next patch version suffixed with '-pre' and commit "now working on x.x.x" |
| 13 |
11. if this is a legacy release, `git merge` changes into master. |
| 14 |
|
| 15 |
## updating the website |
| 16 |
|
| 17 |
For 5.x |
| 18 |
|
| 19 |
0. Change to the master branch |
| 20 |
1. execute `make docs` (when this process completes you'll be on the gh-pages branch) |
| 21 |
2. `git commit -a -m 'chore: website 5.x.x'` |
| 22 |
3. `git push origin gh-pages` |
| 23 |
|
| 24 |
For 4.x |
| 25 |
|
| 26 |
0. Change to the 4.x branch |
| 27 |
1. execute `make docs_legacy` (when this process completes you'll be on the gh-pages branch) |
| 28 |
2. `git commit -a -m 'chore: website 4.x.x'` |
| 29 |
3. `git push origin gh-pages` |