Repository navigation
chore: upstream dfinity/icp-js-canisters moved to 3.6.0 #365
Description
dfinity/icp-js-canisters has moved past the ref the docs are verified against.
Pinned in .sources/upstream.json |
3.5.0 |
| Latest npm release of @icp-sdk/canisters | 3.6.0 |
| Registry | https://www.npmjs.com/package/@icp-sdk/canisters |
| Published reference | https://js.icp.build/canisters/ |
What to re-check
@icp-sdk/canisters APIs, notably AssetManager in references/application-canisters.md and guides/frontends/asset-canister.md, which states a minimum of 3.5.0. This repo's semver tags lag its published versions, so npm is the release signal. Changelog: https://github.com/dfinity/icp-js-canisters/blob/main/CHANGELOG.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
pinnedto3.6.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. No doc impact: 3.6.0 adds NNS converter fields and IC Management snapshot visibility. The stated minimum in
references/application-canisters.mdis>= 3.5.0, which 3.6.0 satisfies, so the text stands. Pin moved to 3.6.0.