chore: upstream dfinity/cdk-rs (ic-cdk-management-canister) moved to 0.3.0
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 72/100
- Issue 類型
- 文件
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- markdown, rust
研究方向
Read .agents/upstream-tracking.md and the changelog sections newer than the 0.2.0 pin, then compare them with guides/backends/https-outcalls.mdx, concepts/https-outcalls.md, references/cycle-costs.md, and the named Rust examples. Update statements affected by the 0.3.0 release and set pinned in .sources/upstream.json to 0.3.0; if the docs are unaffected, the pin bump alone is done.
由索引模型根據 Issue 內容生成。
描述
dfinity/cdk-rs has moved past the ref the docs are verified against.
Pinned in .sources/upstream.json |
0.2.0 |
| Latest crates.io release of ic-cdk-management-canister | 0.3.0 |
| Registry | https://crates.io/crates/ic-cdk-management-canister |
| Published reference | https://docs.rs/ic-cdk-management-canister/latest/ic_cdk_management_canister/ |
What to re-check
The HTTPS outcall APIs in guides/backends/https-outcalls.mdx, concepts/https-outcalls.md and references/cycle-costs.md, and the Rust snippets in the send_http_get, send_http_post and daily_planner examples. This crate versions independently of ic-cdk in the same repo, so it gets its own entry: 0.2.0 replaced the free http_request with the HttpRequest and FlexibleHttpRequest builders and moved pricing to version 2. Read the sections newer than the pin in https://github.com/dfinity/cdk-rs/blob/master/ic-cdk-management-canister/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
pinnedto0.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
- 主要語言
- JavaScript
- 星號
- 4
- 分支
- 5
- 平均合併
- 1 天 16 小時
- 30 天內合併 PR
- 21
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
dfinity/developer-docs 的其他 Issue
-
upstream-dfinity-icp-cli-recipes-static-site upstream-sync
難度 3/5 1-2 天 新手友好度 76/100
dfinity/developer-docs#426 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 55/100
dfinity/developer-docs#281 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 35/100
dfinity/developer-docs#279 ·
維護者通常 1 天內回覆
-
docs: cycle cost docs follow-up — ICP formula, worked example, instruction profiling, cost traps未關閉
難度 4/5 3-5 天 新手友好度 68/100
dfinity/developer-docs#274 ·
維護者通常 1 天內回覆
-
documentation enhancement
難度 4/5 3-5 天 新手友好度 52/100
dfinity/developer-docs#232 · 1 則留言 ·
維護者通常 1 天內回覆
查看 dfinity/developer-docs 的全部 Issue
相似的 Issue
-
Four problem loader browser tests fail on Windows可能已有人在做 @Patriciaath999 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 85/100
juice-shop/juice-shop#3686 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 72/100
TheOdinProject/curriculum#31465 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 88/100
TurboDocx/html-to-docx#254 ·
-
enhancement
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆