This is due to an npm bug, where it believed it had received 0.2.0 but
hadn’t. Unfortunately, it believed it sufficiently as to prevent us from
actually publishing 0.2.0, telling us it was an already-existing
version.