Dependency management

[nickevansuk]

Consider having a more stable dependency management approach between libraries.

Currently every library is released at the bleeding-edge, and there is no check before pushing a new version of one library (e.g. data-models) that is central to many other libraries that it does not create any breaking changes.

We should look at other popular libraries with multiple related components to see how they handle dependency-management, possibly adopting something like a "next" or "beta" channel approach as others do:

• https://reactjs.org/docs/release-channels.html
• https://www.chromium.org/getting-involved/dev-channel

For example, could we have CI run against all components in the dependency tree based on "@ next" or the master / release branch, and ensure that CI passes everywhere before releasing any changed components?

Are there tools that exist, perhaps similar to Lerna, that allow you to push new versions only when something has changed?