WIP

[greg-in-a-box]

Reintroducing the next branch for future features to be worked in isolation and validating releases before merging into master. It seems we need to add in the next branch into the release.config.js also because its not accounting for the next channel when determining which version to set.

https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#branches

i.e. Insurance that updating something like react dependencies work if installed via NPM instead of relying on linking where it would not dedupe. Cannot assume the customer has access to the webpack.config.js either