chore: upstream dfinity/icp-cli-recipes (static-site) moved to static-site-v0.4.0
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 74/100
- Issue 類型
- 文件
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript
研究方向
Start with .agents/upstream-tracking.md and compare static-site-v0.3.3 with static-site-v0.4.0. Re-check the @dfinity/static-site examples in guides/frontends/, getting-started/, and references/application-canisters.md, then update any affected documentation and set pinned to static-site-v0.4.0 in .sources/upstream.json. Done means the reviewed pages are current and the pin is updated in the same PR, or the PR explains why only the pin changed.
由索引模型根據 Issue 內容生成。
描述
dfinity/icp-cli-recipes has moved past the ref the docs are verified against.
Pinned in .sources/upstream.json |
static-site-v0.3.3 |
| Latest release | static-site-v0.4.0 |
| Compare | https://github.com/dfinity/icp-cli-recipes/compare/static-site-v0.3.3...static-site-v0.4.0 |
| 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.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 天內回覆
-
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 天內回覆
查看 dfinity/developer-docs 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 65/100
-
[BUG] Tools returned by input processors get an empty context.agent.agentId可能重新可做 關聯的 PR 已關閉且未合併。 未關閉@mastra/core effort:low impact:medium status: auto-triaged Tools
難度 2/5 1-3 小時 新手友好度 68/100
mastra-ai/mastra#26794 · 3 則留言 ·
維護者通常 1 天內回覆
-
release:v5.34
難度 1/5 1-3 小時 新手友好度 88/100
Jason-Vaughan/TangleClaw#2365 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
-
enhancement
難度 1/5 1-3 小時 新手友好度 85/100
holepunchto/hrpc-test#28 ·