From 98af6a7b4a63248d9ee4f4292805c76cb545ec61 Mon Sep 17 00:00:00 2001 From: Marco Walz Date: Tue, 9 Jun 2026 16:34:32 +0200 Subject: [PATCH] chore: bump icp-cli to v0.3.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Submodule pinned to v0.3.1 (c4c4618) - All CLI doc links updated from /0.2/ to /0.3/ slug (12 files) - @dfinity/asset-canister@v2.1.0 → v2.2.1 in 10 locations: v0.3 removes the built-in `assets` sync step that v2.1.0 emitted internally; v2.2.1 switches to the plugin-based replacement - @dfinity/rust@v3.1.0 → v3.2.0 in project-structure.mdx (consistency fix) --- .sources/VERSIONS | 2 +- .sources/icp-cli | 2 +- docs/developer-tools/index.md | 6 +++--- docs/getting-started/project-structure.mdx | 10 +++++----- docs/getting-started/quickstart.md | 4 ++-- .../parallel-inter-canister-calls.mdx | 4 ++-- .../canister-management/cycles-management.mdx | 4 ++-- docs/guides/canister-management/logs.md | 4 ++-- docs/guides/canister-management/settings.mdx | 2 +- docs/guides/canister-management/snapshots.md | 2 +- docs/guides/frontends/asset-canister.md | 6 +++--- docs/guides/frontends/frameworks.md | 14 +++++++------- docs/guides/testing/pocket-ic.md | 2 +- docs/guides/testing/strategies.md | 2 +- docs/index.mdx | 2 +- docs/references/application-canisters.md | 2 +- 16 files changed, 34 insertions(+), 34 deletions(-) diff --git a/.sources/VERSIONS b/.sources/VERSIONS index e0e830e9..f61c90b6 100644 --- a/.sources/VERSIONS +++ b/.sources/VERSIONS @@ -56,7 +56,7 @@ chain-fusion-signer v0.4.0 a18c52a papi v0.1.1 168bc9d ic-pub-key v1.0.1 f89fa55 -icp-cli v0.2.3 caeac37 +icp-cli v0.3.1 c4c4618 motoko v1.9.0 e7c78d7 motoko-core v2.4.0 cd37dbf cdk-rs ic-cdk v0.20.1 / ic-cdk-timers v1.0.0 / ic-cdk-executor v2.0.0 317f55c diff --git a/.sources/icp-cli b/.sources/icp-cli index caeac373..c4c4618d 160000 --- a/.sources/icp-cli +++ b/.sources/icp-cli @@ -1 +1 @@ -Subproject commit caeac373c450c865c2af97d4f5f68892c613f595 +Subproject commit c4c4618d94c5e05d73544afeb5eb937acad5e140 diff --git a/docs/developer-tools/index.md b/docs/developer-tools/index.md index 6cafe7b9..598e4b6c 100644 --- a/docs/developer-tools/index.md +++ b/docs/developer-tools/index.md @@ -18,13 +18,13 @@ Key features: - **Environments**: named deployment targets that combine a network, canister set, and settings (e.g., local, staging, production) - **Project scaffolding**: `icp new` bootstraps new projects from official templates -For installation, see the [Quickstart](../getting-started/quickstart.md) or the [full CLI documentation](https://cli.internetcomputer.org/0.2/). +For installation, see the [Quickstart](../getting-started/quickstart.md) or the [full CLI documentation](https://cli.internetcomputer.org/0.3/). -Advanced: [creating recipes](https://cli.internetcomputer.org/0.2/guides/creating-recipes) and [creating templates](https://cli.internetcomputer.org/0.2/guides/creating-templates) are documented on the CLI docs site. +Advanced: [creating recipes](https://cli.internetcomputer.org/0.3/guides/creating-recipes) and [creating templates](https://cli.internetcomputer.org/0.3/guides/creating-templates) are documented on the CLI docs site. icp-cli collects anonymous usage telemetry. Opt out with `icp settings telemetry false` or `DO_NOT_TRACK=1`. -Coming from dfx? See the [migration guide](https://cli.internetcomputer.org/0.2/migration/from-dfx). +Coming from dfx? See the [migration guide](https://cli.internetcomputer.org/0.3/migration/from-dfx). ### ic-wasm diff --git a/docs/getting-started/project-structure.mdx b/docs/getting-started/project-structure.mdx index efd3eb58..c8214720 100644 --- a/docs/getting-started/project-structure.mdx +++ b/docs/getting-started/project-structure.mdx @@ -72,7 +72,7 @@ Beyond canisters, `icp.yaml` can also define **networks** (where to deploy) and | `local` | `local` (managed, localhost:8000) | Local development | | `ic` | `ic` (connected, https://icp-api.io) | Mainnet production | -You only need to add custom networks or environments when you have staging environments, testnets, or other deployment targets. See the [icp-cli configuration reference](https://cli.internetcomputer.org/0.2/reference/configuration#networks) for the full schema. +You only need to add custom networks or environments when you have staging environments, testnets, or other deployment targets. See the [icp-cli configuration reference](https://cli.internetcomputer.org/0.3/reference/configuration#networks) for the full schema. ## Canister configuration (canister.yaml) @@ -99,7 +99,7 @@ The Rust backend uses the `@dfinity/rust` recipe: ```yaml name: backend recipe: - type: "@dfinity/rust@v3.1.0" + type: "@dfinity/rust@v3.2.0" configuration: package: backend shrink: true @@ -115,7 +115,7 @@ The frontend uses the `@dfinity/asset-canister` recipe, which builds the fronten ```yaml name: frontend recipe: - type: "@dfinity/asset-canister@v2.1.0" + type: "@dfinity/asset-canister@v2.2.1" configuration: build: - npm install @@ -147,7 +147,7 @@ icp project show This outputs the effective configuration, including all expanded recipe steps and implicit defaults. -Recipes are Handlebars templates hosted at [dfinity/icp-cli-recipes](https://github.com/dfinity/icp-cli-recipes). You can also create local or remote recipes for custom build patterns. See the [icp-cli recipes documentation](https://cli.internetcomputer.org/0.2/guides/creating-recipes) for details. +Recipes are Handlebars templates hosted at [dfinity/icp-cli-recipes](https://github.com/dfinity/icp-cli-recipes). You can also create local or remote recipes for custom build patterns. See the [icp-cli recipes documentation](https://cli.internetcomputer.org/0.3/guides/creating-recipes) for details. ## The .icp/ directory @@ -246,6 +246,6 @@ For a deep dive on binding generation, see [Binding generation](../guides/canist - [Binding generation](../guides/canister-calls/candid.md#binding-generation): deep dive on generating type-safe client code - [Asset canister](../guides/frontends/asset-canister.md): how the frontend recipe and asset upload work - [Canister lifecycle](../guides/canister-management/lifecycle.md): build, deploy, upgrade, and manage canisters -- [icp-cli reference](https://cli.internetcomputer.org/0.2/reference/cli): full CLI and configuration documentation +- [icp-cli reference](https://cli.internetcomputer.org/0.3/reference/cli): full CLI and configuration documentation {/* Upstream: informed by dfinity/icp-cli docs/concepts/project-model.md, docs/concepts/recipes.md, docs/concepts/binding-generation.md, docs/concepts/canister-discovery.md */} diff --git a/docs/getting-started/quickstart.md b/docs/getting-started/quickstart.md index 0d24f622..ab753ae8 100644 --- a/docs/getting-started/quickstart.md +++ b/docs/getting-started/quickstart.md @@ -37,7 +37,7 @@ icp --version ic-wasm --version ``` -> **Alternative methods:** [Homebrew, shell scripts, and other options](https://cli.internetcomputer.org/0.2/guides/installation) are also available. +> **Alternative methods:** [Homebrew, shell scripts, and other options](https://cli.internetcomputer.org/0.3/guides/installation) are also available. ## Create a project @@ -127,6 +127,6 @@ Each canister name maps to a directory containing its own `canister.yaml` with b - [Choose your path](choose-your-path.md): pick a development path based on what you want to build - [Concepts: Canisters](../concepts/canisters.md): learn what canisters are and how they work - [AI coding agents](../guides/ai-coding-agents.md): use ICP skills to build on the Internet Computer with AI -- [icp-cli documentation](https://cli.internetcomputer.org/0.2/): full CLI reference and guides +- [icp-cli documentation](https://cli.internetcomputer.org/0.3/): full CLI reference and guides diff --git a/docs/guides/canister-calls/parallel-inter-canister-calls.mdx b/docs/guides/canister-calls/parallel-inter-canister-calls.mdx index c96b15ae..c93a9ffa 100644 --- a/docs/guides/canister-calls/parallel-inter-canister-calls.mdx +++ b/docs/guides/canister-calls/parallel-inter-canister-calls.mdx @@ -16,13 +16,13 @@ Parallel calls are most beneficial when the caller and callee are on **different -- [icp-cli](https://cli.internetcomputer.org/0.2/guides/installation) installed +- [icp-cli](https://cli.internetcomputer.org/0.3/guides/installation) installed - `mops` package manager with `core = "2.0.0"` in `mops.toml` -- [icp-cli](https://cli.internetcomputer.org/0.2/guides/installation) installed +- [icp-cli](https://cli.internetcomputer.org/0.3/guides/installation) installed - `ic-cdk = "0.19"` and `futures = "0.3"` in `Cargo.toml` diff --git a/docs/guides/canister-management/cycles-management.mdx b/docs/guides/canister-management/cycles-management.mdx index e91e2c0d..29f3f117 100644 --- a/docs/guides/canister-management/cycles-management.mdx +++ b/docs/guides/canister-management/cycles-management.mdx @@ -307,7 +307,7 @@ icp deploy -e staging icp deploy -e production ``` -Each environment maintains separate canister IDs. Mainnet IDs are stored in `.icp/data/mappings/.ids.json` and should be committed to version control. See [Managing environments](https://cli.internetcomputer.org/0.2/guides/managing-environments) for full configuration options. +Each environment maintains separate canister IDs. Mainnet IDs are stored in `.icp/data/mappings/.ids.json` and should be committed to version control. See [Managing environments](https://cli.internetcomputer.org/0.3/guides/managing-environments) for full configuration options. ## Production deployment checklist @@ -375,6 +375,6 @@ icp canister top-up backend --amount 1T -n ic - [Cycles ledger reference](../../references/system-canisters.md#cycles-ledger): Canister IDs and interface specification - [Calls with attached cycles](../canister-calls/inter-canister-calls.md#calls-with-attached-cycles): attach cycles to an inter-canister call and accept them in the callee - [Reproducible builds](reproducible-builds.md): Verify your WASM is trustworthy before deploying -- [icp-cli docs](https://cli.internetcomputer.org/0.2/reference/cli#icp-cycles): Full command reference for `icp cycles` and `icp canister top-up` +- [icp-cli docs](https://cli.internetcomputer.org/0.3/reference/cli#icp-cycles): Full command reference for `icp cycles` and `icp canister top-up` {/* Upstream: informed by dfinity/portal (docs/building-apps/canister-management/topping-up.mdx, docs/building-apps/getting-started/tokens-and-cycles.mdx; dfinity/icp-cli) docs/guides/deploying-to-mainnet.md, docs/guides/tokens-and-cycles.md, docs/guides/managing-environments.md; dfinity/icskills: skills/cycles-management/SKILL.md */} diff --git a/docs/guides/canister-management/logs.md b/docs/guides/canister-management/logs.md index ea2972b0..1bfbf91a 100644 --- a/docs/guides/canister-management/logs.md +++ b/docs/guides/canister-management/logs.md @@ -405,7 +405,7 @@ async fn main() -> Result<()> { - [Canister lifecycle](lifecycle.md): configure log visibility and memory limits when creating or deploying a canister - [Testing strategies](../testing/strategies.md): use canister logs as part of your debugging workflow -- [CLI reference: `icp canister logs`](https://cli.internetcomputer.org/0.2/reference/cli#icp-canister-logs): full command flags and options -- [CLI reference: `icp canister settings update`](https://cli.internetcomputer.org/0.2/reference/cli#icp-canister-settings-update): full command flags and options +- [CLI reference: `icp canister logs`](https://cli.internetcomputer.org/0.3/reference/cli#icp-canister-logs): full command flags and options +- [CLI reference: `icp canister settings update`](https://cli.internetcomputer.org/0.3/reference/cli#icp-canister-settings-update): full command flags and options diff --git a/docs/guides/canister-management/settings.mdx b/docs/guides/canister-management/settings.mdx index 032c9e57..b7a14d64 100644 --- a/docs/guides/canister-management/settings.mdx +++ b/docs/guides/canister-management/settings.mdx @@ -332,7 +332,7 @@ icp canister settings update backend -e ic --freezing-threshold 90d Additional flags: `--reserved-cycles-limit`, `--wasm-memory-threshold`, `--log-memory-limit`, `--add-environment-variable`. Run `icp canister settings update --help` for the full list. -For the full list of CLI flags, see the [icp-cli reference](https://cli.internetcomputer.org/0.2/reference/cli#icp-canister-settings-update). +For the full list of CLI flags, see the [icp-cli reference](https://cli.internetcomputer.org/0.3/reference/cli#icp-canister-settings-update). ## Updating settings programmatically diff --git a/docs/guides/canister-management/snapshots.md b/docs/guides/canister-management/snapshots.md index 6ae039be..f0018831 100644 --- a/docs/guides/canister-management/snapshots.md +++ b/docs/guides/canister-management/snapshots.md @@ -181,6 +181,6 @@ icp canister status my-canister -e ic - [Canister lifecycle](lifecycle.md): Understand how snapshots fit into the upgrade workflow - [Canister migration](canister-migration.md): Complete guide for moving a canister to a different subnet using the snapshot transfer workflow - [Canister upgrades security](../security/canister-upgrades.md): Security considerations when using snapshot-based rollbacks -- [icp-cli canister snapshot reference](https://cli.internetcomputer.org/0.2/guides/canister-snapshots): Full command reference for all snapshot subcommands +- [icp-cli canister snapshot reference](https://cli.internetcomputer.org/0.3/guides/canister-snapshots): Full command reference for all snapshot subcommands diff --git a/docs/guides/frontends/asset-canister.md b/docs/guides/frontends/asset-canister.md index 5ec4a905..54a81a87 100644 --- a/docs/guides/frontends/asset-canister.md +++ b/docs/guides/frontends/asset-canister.md @@ -44,7 +44,7 @@ Define an asset canister using the `@dfinity/asset-canister` recipe in your `icp canisters: - name: frontend recipe: - type: "@dfinity/asset-canister@v2.1.0" + type: "@dfinity/asset-canister@v2.2.1" configuration: dir: dist build: @@ -54,7 +54,7 @@ canisters: The key fields are: -- **`recipe.type`:** specifies the asset canister recipe with a pinned version. Always pin to a specific version (e.g., `@v2.1.0`). See [available versions](https://github.com/dfinity/icp-cli-recipes/releases?q=asset-canister&expanded=true). +- **`recipe.type`:** specifies the asset canister recipe with a pinned version. Always pin to a specific version (e.g., `@v2.2.1`). See [available versions](https://github.com/dfinity/icp-cli-recipes/releases?q=asset-canister&expanded=true). - **`dir`:** the directory containing your build output. This is `dist` for Vite-based projects, `out` for Next.js static exports, or `build` for Create React App. The contents of this directory (not the directory itself) are uploaded to the canister. - **`build`:** shell commands that icp-cli runs before uploading. If omitted, icp-cli uploads whatever is already in `dir` without building. @@ -64,7 +64,7 @@ For a fullstack project with a backend canister, list both in the same `icp.yaml canisters: - name: frontend recipe: - type: "@dfinity/asset-canister@v2.1.0" + type: "@dfinity/asset-canister@v2.2.1" configuration: dir: dist build: diff --git a/docs/guides/frontends/frameworks.md b/docs/guides/frontends/frameworks.md index 5553a8b2..74742201 100644 --- a/docs/guides/frontends/frameworks.md +++ b/docs/guides/frontends/frameworks.md @@ -11,7 +11,7 @@ This guide shows you how to configure your framework's build pipeline, wire up t ## Prerequisites -- [icp-cli](https://cli.internetcomputer.org/0.2/guides/installation) installed: `npm install -g @icp-sdk/icp-cli @icp-sdk/ic-wasm` +- [icp-cli](https://cli.internetcomputer.org/0.3/guides/installation) installed: `npm install -g @icp-sdk/icp-cli @icp-sdk/ic-wasm` - A backend canister deployed (or a static-only site with no backend) - Familiarity with [asset canisters](asset-canister.md) @@ -36,7 +36,7 @@ The [hello-world template](../../getting-started/project-structure.md) uses Reac canisters: - name: frontend recipe: - type: "@dfinity/asset-canister@v2.1.0" + type: "@dfinity/asset-canister@v2.2.1" configuration: build: - npm install @@ -214,7 +214,7 @@ export default { canisters: - name: frontend recipe: - type: "@dfinity/asset-canister@v2.1.0" + type: "@dfinity/asset-canister@v2.2.1" configuration: build: - npm install @@ -246,7 +246,7 @@ This outputs static files to the `out/` directory. canisters: - name: frontend recipe: - type: "@dfinity/asset-canister@v2.1.0" + type: "@dfinity/asset-canister@v2.2.1" configuration: build: - npm install @@ -271,7 +271,7 @@ Export your game from Unity Editor: **File → Build Settings → WebGL → Buil canisters: - name: unity_webgl_template_assets recipe: - type: "@dfinity/asset-canister@v2.1.0" + type: "@dfinity/asset-canister@v2.2.1" configuration: dir: dist build: @@ -293,7 +293,7 @@ Export your game from Godot Editor: **Project → Export → HTML5 → Export Pr canisters: - name: godot_html5_assets recipe: - type: "@dfinity/asset-canister@v2.1.0" + type: "@dfinity/asset-canister@v2.2.1" configuration: dir: dist build: @@ -330,7 +330,7 @@ For sites with no backend canister (portfolios, landing pages, documentation): canisters: - name: frontend recipe: - type: "@dfinity/asset-canister@v2.1.0" + type: "@dfinity/asset-canister@v2.2.1" configuration: build: - npm install diff --git a/docs/guides/testing/pocket-ic.md b/docs/guides/testing/pocket-ic.md index d331037f..9d583a72 100644 --- a/docs/guides/testing/pocket-ic.md +++ b/docs/guides/testing/pocket-ic.md @@ -377,7 +377,7 @@ PocketIC runs on macOS and Linux. Windows is not currently supported for standal ## Connecting to a running network for testing -For end-to-end tests that need a full network with all system canisters, use a containerized network instead of PocketIC. See the [icp-cli containerized networks documentation](https://cli.internetcomputer.org/0.2/guides/containerized-networks) for how to configure Docker-based test networks in `icp.yaml`. +For end-to-end tests that need a full network with all system canisters, use a containerized network instead of PocketIC. See the [icp-cli containerized networks documentation](https://cli.internetcomputer.org/0.3/guides/containerized-networks) for how to configure Docker-based test networks in `icp.yaml`. The containerized network is appropriate when: diff --git a/docs/guides/testing/strategies.md b/docs/guides/testing/strategies.md index 23f86f60..9bcfb28b 100644 --- a/docs/guides/testing/strategies.md +++ b/docs/guides/testing/strategies.md @@ -330,7 +330,7 @@ icp network status docker-test --json For the full containerized network configuration reference: including environment variables, volume mounts, and custom images: see the -[icp-cli containerized networks guide](https://cli.internetcomputer.org/0.2/guides/containerized-networks). +[icp-cli containerized networks guide](https://cli.internetcomputer.org/0.3/guides/containerized-networks). ## Choosing the right approach diff --git a/docs/index.mdx b/docs/index.mdx index 2e485ee6..635e176a 100644 --- a/docs/index.mdx +++ b/docs/index.mdx @@ -39,7 +39,7 @@ Teach your AI coding agent the patterns, APIs, and deployment workflows it needs ## External resources - + diff --git a/docs/references/application-canisters.md b/docs/references/application-canisters.md index 139b8faf..4518344e 100644 --- a/docs/references/application-canisters.md +++ b/docs/references/application-canisters.md @@ -19,7 +19,7 @@ Asset canisters are deployed per-project. There is no global asset canister ID: canisters: - name: frontend recipe: - type: "@dfinity/asset-canister@v2.1.0" + type: "@dfinity/asset-canister@v2.2.1" configuration: dir: dist build: