Automate pre-release build and publishing

[domoscargin]

What

Following work to automate the building and publishing of releases, we should extend this functionality to pre-releases.

There a few outstanding things to do before pre-releases can be fully supported:

Ensuring beta releases publish to the next tag on npm

We can handle this in the existing generate-npm-tag script.

Fix Release notes generation for suffixed release versions

Currently we use regex to look for the previous release, but this is missing version numbers that have suffixes (eg: 5.8.1-internal.0), so generated notes are getting the previous "standard" version changes instead (eg: 5.8.0).

Allow internal releases to release with or without CHANGELOG updates

Beta pre-releases and full releases MUST have changes to the CHANGELOG, but internal pre-releases may or may not have changes. Our releases scripts should allow for this.

Nomenclature

We currently use beta to describe a pre-release, whether it's premajor, preminor or prepatch. For our major releases, we convert major, minor and patch to "Breaking release", "Feature release" and "Fix release" respectively. We should similarly convert the pre-releases increments. Perhaps something like "Beta breaking release", "Beta feature release" and "Beta fix release".

Why

This will cut down on time spent releasing, and reduce risk of human error.

Who needs to work on this

Developers

Who needs to review this

Developers

Done when

• We can run pre-releases via the new automated flow
• We have tested this by dry-running a beta release