Merge pull request #62 from bugsnag/release/v1.8.0

Release v1.8.0

CHANGELOG.md

@@ -1,9 +1,13 @@
 # Changelog
 
+## 1.8.0 (2021-07-07)
+
+- Use webpack for logging (#55)
+- Upgrade build reporter to latest version (#57)
+
 ## 1.7.0 (2021-05-18)
 
 - Update to v2 of @bugsnag/source-maps (#53)
-- Use webpack for logging (#55)
 
 ## 1.6.0 (2020-12-17)
 

CONTRIBUTING.md

@@ -38,3 +38,45 @@ work on your suggested feature.
 That said, we have had some tremendous contributions from the community in the past,
 so use your best judgement. What we want to avoid here is anybody feeling like they’ve
 wasted their time!
+
+## Releases
+
+To start a release:
+
+- decide on a version number
+- create a new release branch from `next` with the version number in the branch name `git checkout -b release/vX.Y.Z`
+- review commits made to `next` since the last release
+- update `CHANGELOG.md` reflecting the above changes, release version, and release date and commit to your release branch
+- make a PR from your release branch to `master` entitled `Release vX.Y.Z`
+- get the release PR reviewed – all code changes should have been reviewed already, this should be a review of the integration of all changes to be shipped and the changelog
+
+Once the release PR has been approved, merge the PR into `master`. You are now ready to make the release. Ensure you are logged in to npm and that you have access to publish the package.
+
+- Make sure you are on the latest `master`.
+
+- Bump the package version and push the new commit and tag:
+
+  ```
+  npm version <major|minor|patch>
+  git push origin master
+  git push --tags
+  ```
+
+- Publish the new version to npm:
+
+  ```
+  npm publish
+  ```
+
+Finally:
+
+- create a release on GitHub https://github.com/bugsnag/webpack-bugsnag-plugins/releases/new
+- Use the existing tag created during the version step above
+- copy the release notes from `CHANGELOG.md`
+- publish the release
+- update and push `next`:
+  ```
+  git checkout next
+  git merge master
+  git push
+  ```