Prepare v2.8.0 (#438)

* bump minor version to v2.8.0

* move release steps to RELEASING, expand upon them

CHANGELOG.md

@@ -1,5 +1,28 @@
 # beeline-nodejs changelog
 
+## 2.8.0 [09-01-2021]
+
+### Improvements
+
+- Support esbuild (#415) [@markandrus](https://github.com/markandrus)
+  - **Note:** The use of any JavaScript bundler will prevent the use of the majority of Beeline auto-instrumentations.
+  The Beeline's API can still be used for generating traces manually for your own application logic.
+
+### Maintenance
+
+- Bump @opentelemetry/core from 0.18.0 to 0.24.0 (#414)
+- Bump pg-query-stream from 4.1.0 to 4.2.1 (#430)
+- Bump husky from 6.0.0 to 7.0.2 (#431)
+- Bump supertest from 6.1.3 to 6.1.6 (#432)
+- Bump libhoney from 2.3.0 to 2.3.2 (#435)
+- Bump eslint from 7.30.0 to 7.32.0 (#434)
+- Bump pg from 8.6.0 to 8.7.1 (#433)
+- Bump lint-staged from 11.0.0 to 11.1.2 (#416)
+- Bump fastify from 3.15.1 to 3.20.2 (#426)
+- Bump @types/node from 16.3.2 to 16.7.1 (#428)
+- Bump jest from 27.0.4 to 27.0.6 (#388)
+- Bump debug from 4.3.1 to 4.3.2 (#404)
+
 ## 2.7.5 [07-23-2021]
 
 ### Fixes

README.md

@@ -24,12 +24,6 @@ CONTRIBUTORS file!
 
 All contributions will be released under the Apache License 2.0.
 
-## Releasing new versions
-
-Use `npm version --no-git-tag-version` to update the version number using `major`, `minor`, `patch`, or the prerelease variants `premajor`, `preminor`, or `prepatch`. We use `--no-git-tag-version` to avoid automatically tagging - tagging with the version automatically triggers a CI run that publishes, and we only want to do that upon merging the PR into `main`.
-
-After doing this, follow our usual instructions for the actual process of tagging and releasing the package.
-
 ## Running postgresql tests locally
 
 If you don't have postgresql running locally, you can launch postgresql in docker.

RELEASING.md

@@ -0,0 +1,15 @@
+# Releasing
+
+- Use `npm version --no-git-tag-version` to update the version number using `major`, `minor`, `patch`, or the prerelease variants `premajor`, `preminor`, or `prepatch`.
+  For example, to bump from v1.1.1 to the next patch version:
+
+```shell
+> npm version --no-git-tag-version patch # 1.1.1 -> 1.1.2
+```
+
+- Confirm the version number update appears in package.json and package-lock.json.
+- Update `CHANGELOG.md` with the changes since the last release.
+- Commit changes, push, and open a release preparation pull request for review.
+- Once the pull request is merged, fetch the updated `main` branch.
+- Apply a tag for the new version on the merged commit: vX.Y.Z, for example v1.1.2.
+- Push the new version tag up to the project repository to kick off build and artifact publishing to GitHub and the NPM registry.

package.json

@@ -6,7 +6,7 @@
     "node": "12.22.1"
   },
   "license": "Apache-2.0",
-  "version": "2.7.4",
+  "version": "2.8.0",
   "repository": {
     "type": "git",
     "url": "https://github.com/honeycombio/beeline-nodejs.git"