1## mongoose release procedure
 2
 31.  tests must pass
 42.  update package.json version
 53.  update History.md using `git changelog` or similar. list the related ticket(s) #<TICKET_NUMBER> as well as a link to the github user who fixed it if applicable.
 64.  git commit -m 'release x.x.x'
 75.  git tag x.x.x
 86.  git push origin BRANCH --tags && npm publish
 97.  update mongoosejs.com (see "updating the website" below)
108.  tweet changelog link from [@mongoosejs](https://twitter.com/mongoosejs)
119. change package.json version to next patch version suffixed with '-pre' and commit "now working on x.x.x"
1210. if this is a legacy release, `git merge` changes into master.
13
14## updating the website
15
16For 4.x
17
180. Change to the master branch
191. execute `make docs` (when this process completes you'll be on the gh-pages branch)
202. `git commit -a -m 'docs: release 4.x.x'`
213. `git push origin gh-pages`
22
23For 3.8.x:
24
250. Change to the 3.8.x branch
261. execute `make docs_legacy` (when this process completes you'll be on the gh-pages branch)
272. `git commit -a -m 'website; regen <x.x.x>'`
283. `git push origin gh-pages`