Cut a v0.11.0+0.1.0 Release

[jbowen93]

Since we have reached a state where we can send transactions, deploy contracts, and call contracts using Optimint as a backend we should create a v0.1.0 release.

Depends on

• Cut a v0.1.0 Release rollkit/rollkit#310
• Create a v0.1.2 Release rollkit/rollkit#323
• Get Ethermint Solidity tests running w/ Ephemeral Cluster #5
• Get RPC tests to pass #7

[jbowen93]

May require a bit of changes to integration tests.

[jbowen93]

Based off the README I believe it will be easiest to run the solidity tests againt the evmos ephemeral cluster within the CI environment.

https://github.com/celestiaorg/devops-test/blob/main/.github/workflows/docker-compose.yml gives an older example of how this can be done.

[jbowen93]

It seems like there are some oddities when attempting to build a v0.1.0 release due to the upstream having had a v0.1.0 release at some point in the past when it was at github.com/cosmos/ethermint.

I believe the best way to keep a sane release pattern is to follow the guidance in this thread and build from upstream releases and append our release number with +0.1.0.

So we should cut a v0.11.0+0.1.0 release.

[jbowen93]

This is done https://github.com/celestiaorg/ethermint/releases/tag/v0.11.0%2B0.1.0