Release 0.0.8

[k88hudson]

Welcome Release Captain! ⛵️

• [x] Assign this issue to yourself.
• [x] Check the VERSION Milestone
  • Any still open issues (except this one) should be merged or moved to a future milestone.
• [x] Checkout and update the main branch locally.
• [x] Update CHANGELOG.md and commit the changes.
  • Use the command git log vPREVIOUS_VERSION.. to see commits between then and now.
  • [x] Note any major changes to the data and schemas.
  • [x] Note any major changes to the library.
  • [x] Add any relevant minor changes.
• [x] Use npm to bump the version. Use one of the following, depending on the version difference:
  • npm version patch - Bug fixes, doc updates, and other small changes.
  • npm version minor - Backwards compatible changes to library features, schemas, or data.
  • npm version major - Breaking changes to library features, schemas, or data.
• [x] Use the commands git push; git push --tags to push your changes to GitHub.
• [ ] Wait for the CI job to publish the new version.
  • https://app.circleci.com/pipelines/github/mozilla/nimbus-shared
• [ ] In #project-nimbus on Slack, write: @here Version VERSION of nimbus-shared has been released on NPM and PyPI.
• [ ] Create a milestone, and a release issue for vNEXT_VERSION with the [release issue template][].
• [ ] Close this issue and the milestone.

[release issue template]: https://github.com/mozilla/nimbus-shared/issues/new?assignees=&labels=&template=release-checklist.md&title=Release+VERSION

[jaredlockhart]

• git push <upstream>;git push <upstream> --tags

[jaredlockhart]

• pushing straight to upstream main bypasses CI checks which results in a broken build artifact which won't deploy (also breaks tests on main)

[mythmon]

These instructions assume you are using the provided pre-commit hook, which prevents this problem. https://mozilla.github.io/nimbus-shared/dev/setup#pre-commit-hook

[jaredlockhart]

That should be explicit in these instructions somewhere because someone just following these instructions can miss that, which we did

[mythmon]

When filing these issues (both this and v0.0.9) remember to replace the ALL_CAPS variables, like version, with the corresponding values (which the instructions say to do).