diff --git a/docs/developer-tools/index.md b/docs/developer-tools/index.md index cb4cc5c7..0d3d2afe 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/1.1/). +For installation, see the [Quickstart](../getting-started/quickstart.md) or the [full CLI documentation](https://cli.internetcomputer.org/1.3/). -Advanced: [creating recipes](https://cli.internetcomputer.org/1.1/guides/creating-recipes) and [creating templates](https://cli.internetcomputer.org/1.1/guides/creating-templates) are documented on the CLI docs site. +Advanced: [creating recipes](https://cli.internetcomputer.org/1.3/guides/creating-recipes) and [creating templates](https://cli.internetcomputer.org/1.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/1.1/migration/from-dfx). +Coming from dfx? See the [migration guide](https://cli.internetcomputer.org/1.3/migration/from-dfx). ### ic-wasm diff --git a/docs/getting-started/project-structure.mdx b/docs/getting-started/project-structure.mdx index 819bbe25..894f9d58 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/1.1/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/1.3/reference/configuration#networks) for the full schema. ## Canister configuration (canister.yaml) @@ -155,7 +155,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/1.1/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/1.3/guides/creating-recipes) for details. ## The .icp/ directory @@ -254,6 +254,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/1.1/reference/cli): full CLI and configuration documentation +- [icp-cli reference](https://cli.internetcomputer.org/1.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 a8c476e6..9c4fc4a7 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/1.1/guides/installation) are also available. +> **Alternative methods:** [Homebrew, shell scripts, and other options](https://cli.internetcomputer.org/1.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/1.1/): full CLI reference and guides +- [icp-cli documentation](https://cli.internetcomputer.org/1.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 ad89e9ef..3ad65f8d 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/1.1/guides/installation) installed +- [icp-cli](https://cli.internetcomputer.org/1.3/guides/installation) installed - `mops` package manager with `core = "2.0.0"` in `mops.toml` -- [icp-cli](https://cli.internetcomputer.org/1.1/guides/installation) installed +- [icp-cli](https://cli.internetcomputer.org/1.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 76a8a39a..8bb4a32f 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/1.1/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/1.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/1.1/reference/cli#icp-cycles): Full command reference for `icp cycles` and `icp canister top-up` +- [icp-cli docs](https://cli.internetcomputer.org/1.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/lifecycle.mdx b/docs/guides/canister-management/lifecycle.mdx index 06cb3636..467dd620 100644 --- a/docs/guides/canister-management/lifecycle.mdx +++ b/docs/guides/canister-management/lifecycle.mdx @@ -264,7 +264,7 @@ This is useful during development when you want a clean slate. The canister ID i Deleting permanently removes a canister from the network. The canister ID cannot be reused. -> **Note:** Canisters are like real estate on the IC. Creating them costs cycles. Instead of deleting a canister, consider reusing it in a different project. Check the [cli reference](https://cli.internetcomputer.org/1.1/concepts/project-model/#canister-ids) for more information. +> **Note:** Canisters are like real estate on the IC. Creating them costs cycles. Instead of deleting a canister, consider reusing it in a different project. Check the [cli reference](https://cli.internetcomputer.org/1.3/concepts/project-model/#canister-ids) for more information. 1. Stop the canister first: diff --git a/docs/guides/canister-management/logs.md b/docs/guides/canister-management/logs.md index 547f819a..85727496 100644 --- a/docs/guides/canister-management/logs.md +++ b/docs/guides/canister-management/logs.md @@ -403,7 +403,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/1.1/reference/cli#icp-canister-logs): full command flags and options -- [CLI reference: `icp canister settings update`](https://cli.internetcomputer.org/1.1/reference/cli#icp-canister-settings-update): full command flags and options +- [CLI reference: `icp canister logs`](https://cli.internetcomputer.org/1.3/reference/cli#icp-canister-logs): full command flags and options +- [CLI reference: `icp canister settings update`](https://cli.internetcomputer.org/1.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 c6f49179..dc9d5f79 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/1.1/reference/cli#icp-canister-settings-update). +For the full list of CLI flags, see the [icp-cli reference](https://cli.internetcomputer.org/1.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 bb1a935d..1bec3f83 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/1.1/guides/canister-snapshots): Full command reference for all snapshot subcommands +- [icp-cli canister snapshot reference](https://cli.internetcomputer.org/1.3/guides/canister-snapshots): Full command reference for all snapshot subcommands diff --git a/docs/guides/digital-assets/ledgers.mdx b/docs/guides/digital-assets/ledgers.mdx index b1ef831e..56384eb7 100644 --- a/docs/guides/digital-assets/ledgers.mdx +++ b/docs/guides/digital-assets/ledgers.mdx @@ -252,7 +252,7 @@ ICRC-2 adds an approve/transferFrom pattern. The asset owner first approves a sp **When to use:** Exchange logic, payment processing, subscription services, or any case where a canister needs to pull assets from a user's account. -> To grant or inspect an allowance manually without writing code, use the [`icp token approve`](https://cli.internetcomputer.org/1.1/reference/cli#icp-token-approve) and [`icp token allowance`](https://cli.internetcomputer.org/1.1/reference/cli#icp-token-allowance) CLI commands. +> To grant or inspect an allowance manually without writing code, use the [`icp token approve`](https://cli.internetcomputer.org/1.3/reference/cli#icp-token-approve) and [`icp token allowance`](https://cli.internetcomputer.org/1.3/reference/cli#icp-token-allowance) CLI commands. diff --git a/docs/guides/frontends/frameworks.md b/docs/guides/frontends/frameworks.md index 3de3037d..c883ebaf 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/1.1/guides/installation) installed: `npm install -g @icp-sdk/icp-cli @icp-sdk/ic-wasm` +- [icp-cli](https://cli.internetcomputer.org/1.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) diff --git a/docs/guides/testing/pocket-ic.md b/docs/guides/testing/pocket-ic.md index da8867be..a40e41e6 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/1.1/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/1.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 202ca6fe..67f12767 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/1.1/guides/containerized-networks). +[icp-cli containerized networks guide](https://cli.internetcomputer.org/1.3/guides/containerized-networks). ## Choosing the right approach diff --git a/docs/index.mdx b/docs/index.mdx index 2e7e55ab..ccecfa76 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 - +