📚 Context
When trying to understand problems that happens to the stack that cartesi cli uses underneath, we need to know which versions of those components are being used so that we can investigate it further.
Looking at the logs is not always easy, since it can be too noisy.
When using cartesi --version, we only get the information about the cli itself.
✔️ Solution
The cartesi --version command could shgow us the versions for internal compnents used:
- cartesi-rollups-node
- cartesi-graphql
- cartesi-espresso-reader
- cartesi-machine-emulator
- cartesi-guest-tools
- ...
Also, some commands can use local binaries or container images, that should also be informed.
📈 Subtasks
🎯 Definition of Done
📚 Context
When trying to understand problems that happens to the stack that cartesi cli uses underneath, we need to know which versions of those components are being used so that we can investigate it further.
Looking at the logs is not always easy, since it can be too noisy.
When using
cartesi --version, we only get the information about the cli itself.✔️ Solution
The
cartesi --versioncommand could shgow us the versions for internal compnents used:Also, some commands can use local binaries or container images, that should also be informed.
📈 Subtasks
doctoroutput, a newversioncommand or reuse--versionargument.🎯 Definition of Done