Jerónimo Albi

> Are these tests for the current or the new client? We might not want to invest in testing Vuex, because it is on its way out. The tests are...

> @jeronimoalbi on my machine, the cosmosgen tests are failing. > Any hint ? Actually no, I will run it locally to see if I can figure it out but...

I think the config of the chain being published should be up to date with the version of the config known by the Ignite CLI binary being used to run...

> What is the query or the transaction you run to trigger this error ? @tbruyelle I got this error while working on an SPN related issue. I was not...

For consistency I would recommend to follow semver even for small packages. Also to avoid any unexpected issues with the go tooling.

Another approach to load the plugins that would allow to get the command execution context could be done in the `ignite/cmd/ignite/main.go` file with something like: ```go func main() { ctx...

Awesome feature @tbruyelle 🥇

@julienrbrt thanks for the updates regarding the `cosmos-sdk` change 👍

> That's a little surprising since the cosmos-sdk v0.50 isn't even released (ony rc1 for now). As of right now we are aiming to first release the CLI with `v0.50`...

The next Ignite CLI release will include #3476 where we migrated from using `protoc` directly to using [Buf.build](https://buf.build/). I think it will potentially fix the issue because we removed the...