Swap release process to release-please

[voxpelli]

I would personally be in favor of switching to a release please flow, like in eslint-community/eslint-plugin-n#305, as that catches errors like this before release

This would help catch release errors like #484 (comment) before they actually get released

[voxpelli]

Thoughts @scagood @aladdin-add @brettz9?

[brettz9]

Looks all right to me...

[scagood]

I do much prefer release-please as:

1. It allows you to see the change logs in the PR description
2. The package version is always correct in the package.json
3. It allows for a more transparent release process

(Also, its just personal comfort 😂)

---

It does have some down sides, such as merge commits occasionally create double entries in the change log.

[ota-meshi]

Between release-please and semantic-release, I personally prefer release-please. Because we can control the release timing.

[voxpelli]

It does have some down sides, such as merge commits occasionally create double entries in the change log.

Yeah, one should preferably only do squash (or rebase commits) with it

[ota-meshi]

Currently, it appears that only squash merging is allowed for this repository.

[voxpelli]

Currently, it appears that only squash merging is allowed for this repository.

That's good 👍