Repository navigation
chore: upstream dfinity/icp-cli moved to v1.3.0 #361
Description
dfinity/icp-cli has moved past the ref the docs are verified against.
Pinned in .sources/upstream.json |
v1.1.0 |
| Latest release | v1.3.0 |
| Compare | dfinity/icp-cli@v1.1.0...v1.3.0 |
| Published reference | https://cli.internetcomputer.org/ |
What to re-check
Every icp command and flag in docs/. A new minor also moves the cli.internetcomputer.org link slug (AGENTS.md 'Linking rules'). NOTE: the doc links were moved to the 1.3 slug in #354, but the commands themselves were last verified against v1.1.0, so the first bump of this pin carries that verification pass.
docs/reference/cli.md
14 line(s) added, 0 removed.
New sections:
##icp canister link``###### **Arguments:**###### **Options:**
Full diff:
diff <(curl -sL https://raw.githubusercontent.com/dfinity/icp-cli/v1.1.0/docs/reference/cli.md) \
<(curl -sL https://raw.githubusercontent.com/dfinity/icp-cli/v1.3.0/docs/reference/cli.md)How to close this
- Review the changes above against the pages named under "What to re-check".
- Update those pages if anything they state has changed.
- Set
pinnedtov1.3.0in.sources/upstream.jsonin the same PR.
If nothing in the docs is affected, bump the pin on its own and say so in the PR.
Procedure: .agents/upstream-tracking.md
Activity
docs: sync content against the ten upstream releases the watcher surf…
marc0olo commentedon Aug 27, 2026
Done in #370.
docs/reference/cli.mdlost 0 lines between v1.1.0 and v1.3.0, so no documented command or flag disappeared. Verifying everyicpinvocation against the reference did surface two that never existed:icp canister id <name>is nowicp canister status <name> -i, andicp identity whoamiis nowicp identity principal, five call sites across three pages. Pin moved to v1.3.0. The doc links were already on the 1.3 slug from #354; this carried the command verification that was deferred there.docs: record that a closing keyword binds to one issue (#371)