2.0.0-alpha.1

[aelesbao]

⚠️ BREAKING CHANGES

• This version of the CLI is a complete rewrite of the whole codebase and is not
  compatible with previous versions. To migrate from v1.* to v2.*, users
  will have to import their keys using the available commands in
  archway accounts, and generate a new config file at the root of the project
  using config init.

Added

• contracts: commands for all stages of contract development and deployment
  (c931552, 47c0b29, 39e81c3, c432704, 54b4486, bb1fda2, 6ac75b3, 364154f, 4efcd0f,
  3a19192)
• rewards: new command to query and withdraw rewards (0e6c993 and 82b0ae3)
• config: added new sub-commands to manage your project config (6bb3000, 59245c3)
• config: support for importing and exporting chain specs (3b1ed5a)
• cli: added the help command (feat: add the help command #207)

Changed

• new: defaults to a workspace project template and changed flags (3aaa062)
• accounts: manages encrypted keys and transfers (82d4ae7, 5346235, 1d116d1,
  7879cbe)

---

This discussion was created from the release 2.0.0-alpha.1.

[appferreira]

First feedback regarding this new CLI version
The installation and process is much smoother than the experience I had with previous versions.
I can see there are many more options than it were, and the separation of subjects makes it feel way more organised than before.
Great job 💪 team 👏

Few suggestions:
1 - please consider, adding to readme.md, dependency: Having docker installed and running, no need to pull docker image as the new CLI does that automatically
2 - please consider, adding to readme.md, detailed information on how to change keyring backend location to file, as some might not be interested in keep those on OS key manager
3 - please consider, changing the os key manager name to something more appealing and informative like "archway-key-manager" or something, because at the moment, my keychain asks permission to use confidential information stored in "" in my keychain, which sounds (MacOS 13.2)

[aelesbao]

Thanks a lot for the feedback, @appferreira! We've been talking about changing how the config works and using global settings (stored in ~/.config/archway/global.json) to set options regarding the keyring and the default chain.

We will follow up on your suggestions in the next pre-release.