chore: upstream dfinity/icp-cli-recipes (static-site) moved to static-site-v0.4.1
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 76/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- javascript
调研方向
Read .agents/upstream-tracking.md, compare the static-site-v0.4.0 and static-site-v0.4.1 release changes, then review the @dfinity/static-site@ examples in guides/frontends/, getting-started/ and references/application-canisters.md. Update any affected pages and set pinned to static-site-v0.4.1 in .sources/upstream.json; if no docs change, the pin bump and an explanation in the PR are done.
由索引模型根据 Issue 内容生成。
描述
dfinity/icp-cli-recipes has moved past the ref the docs are verified against.
Pinned in .sources/upstream.json |
static-site-v0.4.0 |
| Latest release | static-site-v0.4.1 |
| Compare | https://github.com/dfinity/icp-cli-recipes/compare/static-site-v0.4.0...static-site-v0.4.1 |
| Published reference | https://github.com/dfinity/icp-cli-recipes/releases |
What to re-check
The canister's own pages are synced from dfinity/certified-assets into docs/guides/frontends/static-site/ and follow that repo's releases, not this one, so a recipe release mainly moves the version readers pin: check the @dfinity/static-site@ examples in guides/frontends/, getting-started/ and references/application-canisters.md. This repo's own icp.yaml deploys with it, so a release also affects the docs site itself. 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
pinnedtostatic-site-v0.4.1in.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-cdk-rs-ic-cdk-management-canister upstream-sync
难度 3/5 1-2 天 新手友好度 72/100
dfinity/developer-docs#425 ·
维护者通常 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
-
[BUG]: Prompt compressor crashes with TypeError when a past chat has a non-string response.text可能已有人在做 @ManojDevarajulu 今天认领。 未关闭possible bug
难度 2/5 1-3 小时 新手友好度 82/100
Mintplex-Labs/anything-llm#6737 ·
维护者通常 1 天内回复
-
check:passed feeds:add
难度 2/5 1 小时以内 新手友好度 62/100
-
难度 2/5 1-3 小时 新手友好度 74/100
motiondivision/motion#3935 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 70/100
codex-team/editor.js#3037 ·
-
No Code Attached Yet
难度 2/5 1-3 小时 新手友好度 72/100
joomla/joomla-cms#48626 ·
维护者通常 1 天内回复