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
-
good first issue
难度 1/5 1 小时以内 新手友好度 88/100
saayam-for-all/webapp#1919 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
Uuriko/project-room#3728 ·
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 62/100
devops-thiago/ThrillhouseBot#1132 ·
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 74/100
andromarces/agent-loops#886 ·
维护者通常 1 天内回复
-
bug effort:low model:light plan planner:gpt-6-1-sol tests
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复