Sync Changelog

Overview

kimi-code uses changesets for versioning. Each package gets its own CHANGELOG.md. The user-facing CLI package, @moonshot-ai/kimi-code, writes its changelog here:

apps/kimi-code/CHANGELOG.md

This file is the only upstream source for the documentation-site changelog. Internal package changelogs such as packages/*/CHANGELOG.md do not go into the documentation site.

After the release flow finishes (Release PR merged → Version Packages completed → npm publish succeeded), maintainers manually run this skill to copy the new CLI changelog entries into the docs site, translate the English increment into Chinese, wait for an optional human review, then commit on a dedicated branch and open a PR.

When To Use

• A new version has been published to npm.
• The top of apps/kimi-code/CHANGELOG.md contains version blocks that are not yet in docs/en/release-notes/changelog.md.
• The gen-docs flow does not run this automatically; maintainers must explicitly do it after release.

Do not run this before the Release PR is merged. At that point, changesets has not yet written the new version into apps/kimi-code/CHANGELOG.md.

Source And Targets

File	Role	Edited by
apps/kimi-code/CHANGELOG.md	Only upstream source, generated by changesets	Never edit manually
docs/en/release-notes/changelog.md	English docs changelog; source of truth for docs	This skill
docs/zh/release-notes/changelog.md	Chinese docs changelog, translated from English	This skill, following translate-docs

Core rule: the English docs changelog is the source of truth, and Chinese is translated from English. This matches translate-docs.

Preconditions

Before editing, confirm:

• The released version exists on npm (npm view @moonshot-ai/kimi-code versions --json) or has a matching GitHub Release tag.
• The top of apps/kimi-code/CHANGELOG.md is that new version.