Release procedure

mongoose release procedure

tests must pass
update package.json and package-lock.json version
update CHANGELOG.md. 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
create a new release on GitHub - this will automatically deploy to npm for 8.x and 9.x
update mongoosejs.com (see "updating the website" below)
tweet changelog link from @mongoosejs
Announce on mongoosejsteam slack channel
if this is a legacy release, git merge changes into master.

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

For 8.x

Change to the 8.x branch
execute npm run docs:prepare:publish:8x (when this process completes you'll be on the gh-pages branch)
git commit -a -m 'chore: website 8.x.x'
git push origin gh-pages

create docs/migrating_to_x.md
update default version in docs/js/search.js
create branch for previous major version, like 9.x
update previous major version branch's publish.yml to publish to a tag that isn't latest, like 9x or similar