1.0.6

[Amxx]

I'd like to release the current version so we can move forward with testing in OpenZeppelin/openzeppelin-contracts#3617

[ernestognw]

Yeah, let's merge this and continue with the MerkleTree builder PR

[frangio]

FYI, this repo is released manually via npm version + npm publish. Pushing the tag will create a GitHub release automatically.

[Amxx]

FYI, this repo is released manually via npm version + npm publish. Pushing the tag will create a GitHub release automatically.

There is a security thing preventing me from pushing directly to master.

I wanted to do:

• nom version
• git push
• npm publish
  But step 2 was blocked and it did not feel right to publish a commit that is not on the master branch.

That is why I created this PR and planned to tag and publish the commit that result from this being merged. It that ok or should we do the release differently ?

[frangio]

Yes that sounds good!