Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

chore: upstream dfinity/motoko-core moved to v2.6.2

未关闭
#404 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
72/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
领域
documentation

调研方向

Read .agents/upstream-tracking.md, then compare motoko-core v2.6.1 with v2.6.2 using the provided Changelog.md command and review every mo:core import and API signature in the documentation code blocks. Update any affected pages and set pinned to v2.6.2 in .sources/upstream.json; if nothing changed, submit the pin update and note that in the PR.

由索引模型根据 Issue 内容生成。

描述

upstream-dfinity-motoko-core upstream-sync

dfinity/motoko-core has moved past the ref the docs are verified against.
Pinned in .sources/upstream.json v2.6.1
Latest release v2.6.2
Compare https://github.com/dfinity/motoko-core/compare/v2.6.1...v2.6.2
Published reference https://mops.one/core/docs

What to re-check

Every mo:core import and API signature in Motoko code blocks.

Changelog.md

3 line(s) added, 0 removed.

New sections:

  • 2.6.2

Full diff:

diff <(curl -sL https://raw.githubusercontent.com/dfinity/motoko-core/v2.6.1/Changelog.md) \
     <(curl -sL https://raw.githubusercontent.com/dfinity/motoko-core/v2.6.2/Changelog.md)

How to close this

  1. Review the changes above against the pages named under "What to re-check".
  2. Update those pages if anything they state has changed.
  3. Set pinned to v2.6.2 in .sources/upstream.json in 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 天 5 小时
30 天内合并 PR
36

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

dfinity/developer-docs 的其他 Issue

查看 dfinity/developer-docs 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。