chore: upstream dfinity/icp-js-canisters moved to 4.1.0
Maintainers usually reply within 10 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 77/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- documentation
Research direction
Read .agents/upstream-tracking.md and compare the upstream changelog and published reference with references/application-canisters.md and guides/frontends/asset-canister.md, focusing on AssetManager and the stated minimum version. Update affected documentation and set pinned to 4.1.0 in .sources/upstream.json; if the docs remain accurate, bump only the pin. Done when the changes and pin are included in the same PR.
Written by the indexing model from the issue text.
Description
dfinity/icp-js-canisters has moved past the ref the docs are verified against.
Pinned in .sources/upstream.json |
4.0.0 |
| Latest npm release of @icp-sdk/canisters | 4.1.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
pinnedto4.1.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
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 4
- Avg merge
- 11d 2h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dfinity/developer-docs
-
upstream-dfinity-icp-cli upstream-sync
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
dfinity/developer-docs#441 ·
Maintainers usually reply within 10 days
-
upstream-dfinity-icp-js-core upstream-sync
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dfinity/developer-docs#432 ·
Maintainers usually reply within 10 days
-
upstream-dfinity-icp-cli-recipes-static-site upstream-sync
Difficulty 3/5 1-2 days Newbie friendliness 76/100
dfinity/developer-docs#445 ·
Maintainers usually reply within 10 days
-
upstream-dfinity-motoko-core upstream-sync
Difficulty 3/5 1-2 days Newbie friendliness 68/100
dfinity/developer-docs#431 ·
Maintainers usually reply within 10 days
-
chore: upstream dfinity/cdk-rs (ic-cdk-management-canister) moved to 0.3.0Possibly taken @eichhorl claimed this 32 days ago. Openupstream-dfinity-cdk-rs-ic-cdk-management-canister upstream-sync
Difficulty 3/5 1-2 days Newbie friendliness 72/100
dfinity/developer-docs#425 ·
Maintainers usually reply within 10 days
All issues in dfinity/developer-docs
Similar issues
-
🧩 Docs job fails type-checking `generate-plugin-docs.ts`Possibly taken @X-Guardian claimed this today. Opendiscussion
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
msys2/setup-msys2#673 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
inveniosoftware/invenio-app-rdm#3630 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5522 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Dayset/ps2-elite-kd#119 ·