mongoose release procedure

tests must pass
update package.json and package-lock.json version
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.
git commit -a -m 'release x.x.x'
git tag x.x.x
npm run release, or npm run release-legacy for 4.x
update mongoosejs.com (see "updating the website" below)
tweet changelog link from @mongoosejs
Announce on mongoosejsteam slack channel
change package.json version to next patch version suffixed with '-pre' and commit "now working on x.x.x"
if this is a legacy release, git merge changes into master.

updating the website

For 5.x

Change to the master branch
execute make docs (when this process completes you'll be on the gh-pages branch)
git commit -a -m 'chore: website 5.x.x'
git push origin gh-pages

For 4.x

Change to the 4.x branch
execute make docs_legacy (when this process completes you'll be on the gh-pages branch)
git commit -a -m 'chore: website 4.x.x'
git push origin gh-pages