chore: bump icp-cli to v1.1.0 and update CLI docs

.agents/submodule-bumping.md

@@ -52,7 +52,7 @@ EOF
 
 All CLI docs links use a versioned slug (e.g. `https://cli.internetcomputer.org/0.2/...`). When bumped to a new minor version:
 
-1. Read the new slug: `cat .sources/icp-cli/docs-site/versions.json` — use the `"version"` marked `"latest": true`.
+1. Determine the new slug: it is the `major.minor` of the release tag you pinned (e.g. `v1.1.0` → `1.1`). Do **not** read it from `.sources/icp-cli/docs-site/versions.json` — at a release tag that file still lists the *previous* slug, since the docs-site version bump lands as a follow-up commit after the tag. Confirm the new slug is live by opening the docs-site root (`https://cli.internetcomputer.org/`), which redirects to the latest version.
 2. Verify all linked paths still exist in the new submodule before replacing:
    ```bash
    grep -roh "cli\.internetcomputer\.org/[0-9][.0-9]*/[^\"' )#]*" docs/ --include="*.md" --include="*.mdx" \
@@ -62,10 +62,12 @@ All CLI docs links use a versioned slug (e.g. `https://cli.internetcomputer.org/
        done
    ```
    Resolve any MISSING paths manually before proceeding.
-3. Replace the slug across all files:
+3. Replace the slug across all files (per-file loop — portable across GNU and BSD/macOS `sed`, whose `-i` syntax differs):
    ```bash
-   old=0.2; new=0.3
-   find docs/ \( -name "*.md" -o -name "*.mdx" \) | xargs sed -i "s|cli.internetcomputer.org/${old}/|cli.internetcomputer.org/${new}/|g"
+   old=1.0; new=1.1
+   grep -rl "cli.internetcomputer.org/${old}/" docs/ --include="*.md" --include="*.mdx" | while IFS= read -r f; do
+     sed -i.bak "s|cli.internetcomputer.org/${old}/|cli.internetcomputer.org/${new}/|g" "$f" && rm -f "$f.bak"
+   done
    ```
 4. Run `npm run build` to confirm no broken links.
 

.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               v1.0.0                                                    9eed60c
+icp-cli               v1.1.0                                                    fe4af7c
 motoko                v1.11.0                                                     c3a6eb3
 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

AGENTS.md

@@ -171,7 +171,7 @@ EOF
 - Link to `internetcomputer.org/docs/` (retired) or `learn.internetcomputer.org` (content is now in this repo under `docs/concepts/`)
 - Link to internal pages that don't exist — run `ls <target>` before linking. Links to `.mdx` files use `.md` extension.
 - Link to an internal page without checking for a relevant section anchor — read the target page to find the most specific section that fits, then derive the anchor slug from its heading (lowercase, spaces → `-`, special chars stripped).
-- Link to `https://cli.internetcomputer.org/` bare root — use the versioned path. Current slug: `0.2`; verify with `cat .sources/icp-cli/docs-site/versions.json`.
+- Link to `https://cli.internetcomputer.org/` bare root — use the versioned path. Current slug: `1.1` (the `major.minor` of the pinned icp-cli release). Do not trust `.sources/icp-cli/docs-site/versions.json` here: at a release tag it still lists the *previous* slug, because the docs-site version bump lands as a follow-up commit after the tag. Confirm the live slug at the docs-site root (it redirects to the latest version).
 - Link externally when an internal page exists — check `docs/` first
 - Write em-dashes (`—`) or use `--` as prose punctuation — use colon, semicolon, or parentheses instead. (`--` is fine inside code blocks as a CLI flag or comment.)
 - Rename Candid field names, management canister API identifiers, or example repo names — these are protocol-level identifiers

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.3/).
+For installation, see the [Quickstart](../getting-started/quickstart.md) or the [full CLI documentation](https://cli.internetcomputer.org/1.1/).
 
-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.
+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.
 
 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.3/migration/from-dfx).
+Coming from dfx? See the [migration guide](https://cli.internetcomputer.org/1.1/migration/from-dfx).
 
 ### ic-wasm
 

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.3/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.1/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/0.3/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.1/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/0.3/reference/cli): full CLI and configuration documentation
+- [icp-cli reference](https://cli.internetcomputer.org/1.1/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 */}

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.3/guides/installation) are also available.
+> **Alternative methods:** [Homebrew, shell scripts, and other options](https://cli.internetcomputer.org/1.1/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.3/): full CLI reference and guides
+- [icp-cli documentation](https://cli.internetcomputer.org/1.1/): full CLI reference and guides
 
 <!-- Upstream: informed by dfinity/icp-cli docs/quickstart.md, docs/tutorial.md -->

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
 <Tabs syncKey="lang">
 <TabItem label="Motoko">
 
-- [icp-cli](https://cli.internetcomputer.org/0.3/guides/installation) installed
+- [icp-cli](https://cli.internetcomputer.org/1.1/guides/installation) installed
 - `mops` package manager with `core = "2.0.0"` in `mops.toml`
 
 </TabItem>
 <TabItem label="Rust">
 
-- [icp-cli](https://cli.internetcomputer.org/0.3/guides/installation) installed
+- [icp-cli](https://cli.internetcomputer.org/1.1/guides/installation) installed
 - `ic-cdk = "0.19"` and `futures = "0.3"` in `Cargo.toml`
 
 </TabItem>

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/<environment>.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.
+Each environment maintains separate canister IDs. Mainnet IDs are stored in `.icp/data/mappings/<environment>.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.
 
 ## 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.3/reference/cli#icp-cycles): Full command reference for `icp cycles` and `icp canister top-up`
+- [icp-cli docs](https://cli.internetcomputer.org/1.1/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 */}

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.0/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.1/concepts/project-model/#canister-ids) for more information.
 
 1. Stop the canister first:
 
@@ -278,7 +278,7 @@ icp canister stop my-canister -e ic
 icp canister delete my-canister -e ic
 ```
 
-> **Warning** The remaining cycles in the canister are lost, see [github issue](https://github.com/dfinity/icp-cli/issues/431).
+> **Note:** As of icp-cli v1.1.0, the canister's remaining cycles are returned to the caller (the identity that made the delete request) via the cycles ledger. Pass `--no-recover-cycles` to skip recovery and burn the cycles instead. On earlier versions, the remaining cycles are lost.
 
 ## Migrate a canister between subnets
 

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/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
+- [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
 
 <!-- Upstream: informed by dfinity/portal — docs/building-apps/canister-management/logs.mdx, docs/building-apps/canister-management/backtraces.mdx, docs/building-apps/advanced/canister-access-logs.mdx; dfinity/examples — rust/canister_logs, motoko/canister_logs, rust/query_stats, motoko/query_stats; dfinity/cdk-rs — ic-cdk/src/api.rs, ic-cdk/src/management_canister.rs, ic-management-canister-types/src/lib.rs; dfinity/icp-cli — docs/reference/cli.md, docs/reference/canister-settings.md -->

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.3/reference/cli#icp-canister-settings-update).
+For the full list of CLI flags, see the [icp-cli reference](https://cli.internetcomputer.org/1.1/reference/cli#icp-canister-settings-update).
 
 ## Updating settings programmatically
 

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.3/guides/canister-snapshots): Full command reference for all snapshot subcommands
+- [icp-cli canister snapshot reference](https://cli.internetcomputer.org/1.1/guides/canister-snapshots): Full command reference for all snapshot subcommands
 
 <!-- Upstream: informed by dfinity/icp-cli docs/guides/canister-snapshots.md; dfinity/portal docs/building-apps/canister-management/snapshots.mdx -->

docs/guides/digital-assets/ledgers.mdx

@@ -252,6 +252,8 @@ 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.
+
 <Tabs syncKey="lang">
 <TabItem label="Motoko">
 

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.3/guides/installation) installed: `npm install -g @icp-sdk/icp-cli @icp-sdk/ic-wasm`
+- [icp-cli](https://cli.internetcomputer.org/1.1/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)
 

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.3/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.1/guides/containerized-networks) for how to configure Docker-based test networks in `icp.yaml`.
 
 The containerized network is appropriate when:
 

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.3/guides/containerized-networks).
+[icp-cli containerized networks guide](https://cli.internetcomputer.org/1.1/guides/containerized-networks).
 
 ## Choosing the right approach
 

docs/index.mdx

@@ -39,7 +39,7 @@ Teach your AI coding agent the patterns, APIs, and deployment workflows it needs
 ## External resources
 
 <CardGrid>
-  <LinkCard title="ICP CLI" description="Command-line tool for ICP development" href="https://cli.internetcomputer.org/0.3/" />
+  <LinkCard title="ICP CLI" description="Command-line tool for ICP development" href="https://cli.internetcomputer.org/1.1/" />
   <LinkCard title="JS SDK" description="JavaScript/TypeScript libraries for ICP" href="https://js.icp.build" />
   <LinkCard title="ICP Skills" description="Skills for agents that write code on ICP" href="https://skills.internetcomputer.org" />
   <LinkCard title="Examples" description="Working Motoko and Rust canister examples" href="https://github.com/dfinity/examples" />