Closed joehan closed 4 years ago
Looks like we had something go wrong with a merge at some point - v0.2.1 has already been released, but package.json still showed 0.2.0.
Looks like we had something go wrong with a merge at some point - v0.2.1 has already been released, but package.json still showed 0.2.0.