Version update to 2.0.6 (#165)

Incrementing subpackages to new version (#164)

Upgrade all scoped packages to 2.0.4 as well

Release action now sets NPM version using the tag from the release pr…

…ocess

Release action now sets NPM version using the tag from the release pr…

…ocess

Fix issue where HOSTS_VERSION was incompatible with packages not usin…

…g webpack. (#142)

We were setting the HOSTS_VERSION at build time using webpack.

We also want customers who want to use modules/not use our webpack build to be able to do so.

These are incompatible.

To solve this, we are now writing out the version number into source at release time.
This should have the same effect as before, anyone using an NPM release will get a version number, otherwise you will have 'development'.

I tested this in a release in my fork, you can see the overwritten file here in the artifacts: https://github.com/prestomation/amazon-sumerian-hosts/actions/runs/3301290701

Change Instances of "mainline" to "mainline2.0" (#127)

* Change Instances of "mainline" to "mainline.20"

Upgrade NPM Publish Node Version

Merge pull request #76 from brhook-aws/upgradeNodeVersion

Bump package version to 1.3.6

Merge pull request #49 from jkerste/mainline

Bumping version to 1.3.5