Repository navigation
chore: upstream dfinity/icp-cli-recipes (asset-canister) moved to asset-canister-v2.3.0 #366
Description
dfinity/icp-cli-recipes has moved past the ref the docs are verified against.
Pinned in .sources/upstream.json |
asset-canister-v2.2.1 |
| Latest release | asset-canister-v2.3.0 |
| Compare | dfinity/icp-cli-recipes@asset-canister-v2.2.1...asset-canister-v2.3.0 |
| Published reference | https://github.com/dfinity/icp-cli-recipes/releases |
What to re-check
Cited in 10 places across docs/, including references/application-canisters.md and guides/frontends/asset-canister.md. The legacy frontend recipe; static-site supersedes it. Each recipe in this repo tags and releases on its own prefix, so it gets its own entry: a single pattern across prefixes would compare rust- against static-site- textually and only ever surface one of them.
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
pinnedtoasset-canister-v2.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. The release is one additive change, an optional
visibilityfield on metadata entries, so theicp.yamlexamples stay valid and only the version string moved: 10 occurrences of@dfinity/asset-canister@v2.2.1are now@v2.3.0. Pin moved to asset-canister-v2.3.0.