[chore] Document release workflow

[hamlim]

Benefit:

Future contributors know how to make a new release (and publish to NPM) when necessary

Deliverable:

Add a section to the Contributing guidelines for how the release workflow works

[hamlim]

As I understand the workflow I think we need to do the following:

• Make changes
• Document those changes in the Unreleased section of the Changelog
• When we're ready for a release we;
  • Move all the unreleased changelogs under a new heading for the new version
  • Bump the version in package.json
  • Get this reviewed and merged into main
  • Start a new release from GitHub.com (creating a new git tag for the version we're releasing, e.g. v0.7.0)
  • Fill out the GitHub release info and submit

I think at that point the release GitHub action will run and publish the package to NPM!

[github-actions]

Automatically marking issue as stale due to lack of activity

[hamlim]

Not stale, but might not be acted upon soon.

[github-actions]

Automatically marking issue as stale due to lack of activity

[github-actions]

Automatically closing this issue as stale