icp-cli v0.3.0 is released
Hi folks,
I’m excited to announce that icp-cli v0.3.0 is released. As usual, it’s on npm already and will be available on homebrew soon.
We’re planning for this to be the last 0.x release before an official v1.0 next week. Read on for important information.
Agent skills and icp-cli docs have been updated.
Highlights
Breaking change to asset syncing
First a reminder that it’s been our goal for icp-cli to decouple to the cli tool from the build toolchains, local network runtimes… and as of this release from the asset canister.
The asset canister is probably one of the most used canisters in the ecosystem. Until this release syncing assets was built into the cli tool which meant that the cli had to maintain compatibility with the asset canister. That deep coupling is no longer necessary with the introduction of the “sync plugins”. Going forward the sync process will happen through a sandbox wasm plugin and lives outside of the cli itself.
What this means to you
- In your icp.yaml configuration, the sync step of type “assets” no longer works. You’ll get an error message about it.
- If you are using the @dfinity/asset-canister recipe, you should upgrade to v2.2.1
Consult the migration guide: Upgrading from icp-cli 0.2 | ICP CLI
Login with Internet Identity
You are now able to link a web identity and use it with icp-cli. This means your principal in icp-cli will be the same principal that you would get if you had logged in through the web UI.
This is great if you want to programmatically interact with a canister without having to grant permissions to yet another identity.
More information here: Linking Web Based Identities