/node_modules/mongoose/release-items.md

https://bitbucket.org/coleman333/smartsite · Markdown · 29 lines · 23 code · 6 blank · 0 comment · 0 complexity · 835650827a0f86017885b4d67a636a0a MD5 · raw file

  1. ## mongoose release procedure
  2. 1. tests must pass
  3. 2. update `package.json` and `package-lock.json` version
  4. 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.
  5. 4. git commit -a -m 'release x.x.x'
  6. 5. git tag x.x.x
  7. 6. `npm run release`, or `npm run release-legacy` for 4.x
  8. 7. update mongoosejs.com (see "updating the website" below)
  9. 8. tweet changelog link from [@mongoosejs](https://twitter.com/mongoosejs)
  10. 9. Announce on mongoosejsteam slack channel
  11. 10. change package.json version to next patch version suffixed with '-pre' and commit "now working on x.x.x"
  12. 11. if this is a legacy release, `git merge` changes into master.
  13. ## updating the website
  14. For 5.x
  15. 0. Change to the master branch
  16. 1. execute `make docs` (when this process completes you'll be on the gh-pages branch)
  17. 2. `git commit -a -m 'chore: website 5.x.x'`
  18. 3. `git push origin gh-pages`
  19. For 4.x
  20. 0. Change to the 4.x branch
  21. 1. execute `make docs_legacy` (when this process completes you'll be on the gh-pages branch)
  22. 2. `git commit -a -m 'chore: website 4.x.x'`
  23. 3. `git push origin gh-pages`