Closed tangjeff0 closed 5 years ago
For some reason, npm publish created a new commit but did not autotag itself v1.3.9, thus preventing CircleCI from autopublishing the newest version of the package. Also, there was an extra console.log in the tests.
npm publish
v1.3.9
For some reason,
npm publish
created a new commit but did not autotag itselfv1.3.9
, thus preventing CircleCI from autopublishing the newest version of the package. Also, there was an extra console.log in the tests.