Publishing compute-baseline

[foolip]

@rviscomi wanted to try out compute-baseline, and it turns out we haven't published it to NPM since 0.1.1.

Here's what I'm going to do:

• Tag 8f12268 as compute-baseline/v0.1.1
• Tag 223983d as compute-baseline/v0.2.0 and publish that to NPM. This is just to avoid confusion if we publish 0.2.0 now despite package.json changing a long time ago.
• Bump the version to 0.3.0 and tag/publish that

I think publishing is done with npm publish --workspace compute-baseline.

@ddbeck if any of this is wrong, let's document the right way when you're back :)

[foolip]

I've done the steps I listed now, but leaving this open for @ddbeck to see and say if I did something wrong.

[ddbeck]

This is correct in the sense that it's a method that could be followed to publish compute-baseline. We don't really have a process for doing it though, like we do for web-features package. We could document this (which is why I labeled this documentation), but we'd probably want to regularize things (e.g., write release notes) like we do for web-features. I'm not sure what we'd want to include in that process.