I was thinking about this a bit, and as a user who may potentially try to go both routes (npm and GitHub clone), there might be some value in us trying to keep those in sync, just so users can map between the two (say someone wants to contribute back to a version of the SDK, for instance). For package specific updates, we could rev the version on GitHub too (might be a minor version increment - but I expect this to be fairly isolated - or we can try to do this as part of our release cycle itself). I'm leaning towards trying to keep the version numbers synched across both (starting with 2.0.0), the more I think about it :-)