chore: release 6.9.0

[release-please]

🤖 I have created a release *beep* *boop*

6.9.0 (2020-04-17)

Features

• add support for buffer configuration (#1372) (101aa1a)
• update dependencies / general cleanup (#1356) (42f49b4)

Bug Fixes

• allow file-level options everywhere in the file (b70eebd)
• Import Long types (1d98cb8)
• npm audit fixes (ca52447)
• properly iterate and return method descriptors (d96bb7a)
• run npm audit fix (#1208) (b5b6632)
• docs: update CHANGELOG to match format of release-please (#1376) (15ed8a0)

---

This PR was generated with Release Please.

[bcoe]

This PR is magical ⭐️, It's generated automatically by the tool release-please, based on the commit history (it understands conventional commits which we've been starting to use for newer commits we land).

When landed, this PR will automatically create a GitHub release, but will not yet publish to npm; this is an option for us to setup in the future if we would like, and we're getting good about labeling our commits.

CC: @dcodeIO, wanted to make sure you're in the loop on this update, and are okay with the approach.

[bcoe]

It didn't do a good job of detecting the starting point of the old CHANGELOG, we will be submitting a PR to fix this.

[dcodeIO]

I for one welcome our new robot overlords. Perhaps it makes sense to give #1356 a look before tagging a 6.9.0?

[bcoe]

@dcodeIO sounds good, we can hold our horses before we merge this. @alexander-fenster and I were talking about maybe adding a feature where you could add a tag and create a candidate release from this PR, without merging it, so folks could:

npm i protobufjs@next

[bcoe]

@dcodeIO are you comfortable with this slight change in template template format going forward, we no longer have the #️⃣.

It is possible to add new templates to release-please which match your old format more closely, it's a few hours of work mind you (and I'd only do it if this change in formatting drives you up the wall).

[alexander-fenster]

I have just released 6.9.0-pre as next from this branch to run some integration tests on our side. Looks good so far, I think we can proceed with releasing 6.9.0. @bcoe

[publish-bot]

A candidate release, 6.9.0-beta.0 was published to npm. Run npm install protobufjs@next to install.

[alexander-fenster]

We ran all kinds of integration tests and we're pretty sure it's safe to release it, but let's still do it on Monday and not on Friday :) As soon as this PR is merged, the robot will do its job and we'll officially declare auto-publishing working.