react-sdk latest tag points at previous release

[ZebraFlesh]

The examples all point to the 0.3.0-beta1 release of react-sdk, but the dist-tags still list 0.2.0-beta1 as the latest version:

> yarn info @optimizely/react-sdk dist-tags
yarn info v1.12.1
{ latest:
   '0.2.0-beta1',
  beta:
   '0.3.0-beta1' }
Done in 0.88s.

Is this intentional?

[mjc1283]

Hi ZebraFlesh,

We released v0.3.0-beta1 to gather some early feedback from our users who are interested in upcoming changes. It’s not quite ready for full release yet, so we left the latest dist-tag poitnting to 0.2.0-beta1. Apologies for the confusing state of the examples. If you’re interested, please refer to the examples directory in this prior commit (https://github.com/optimizely/fullstack-labs/tree/bab1fc42f8ca0cd980bb7c956c7fcdb36c0cc340/packages/react-sdk), which are still compatible with 0.2.0-beta1.

[ZebraFlesh]

This is made worse by the 0.2.0-beta1 release not being tagged in github. :(