Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
#404 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
JavaScript
Stars
4
Forks
5
Avg merge
1d 5h
Merged PRs (30d)
36

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dfinity/developer-docs

All issues in dfinity/developer-docs

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.