Architectural Decision Records

2022-06-30 Independent versioning of packages

This way we can consolidate more UI libs in the monorepo and maintain semver for them.
We will no longer republish all @synthetixio/* libs together with synthetix release (so versions will no longer match).
We will only update and release ones that directly or indirectly depend on it. Example is in the README.md.
Github actions will have 2 separate publishing flows:
- to update all pakcages based on desired synthetix version
- to update and publish one single package (and all that depend on it) by name

Because codegen-graph-ts depends on wei and queries depend on codegen-graph-ts we ended up having multiple wei instances of different versions in the lockfile
Adding package to the monorepo is a 3-step process. See details in the README.md

As it turns out NPM workspaces do not have a lot of features
Non-trivial to find all the workspaces in the monorepo (not too problematic)
NPM keeps all deps in a non-flat tree structure, so it is pretty hard to work with when checking dependencies for version mismatches
The biggest problem is publishing new versions as NPM does not update workspaces with new versions automatically, to deal with it, we would require some extra 3rd party tooling
Yarn Berry (v3) resolves all the issues above
Yarn comes with a possibility of zero installs if we opt in to keep packages cache in git