Skip to content

docs(changelog): sync 0.4.0 from apps/kimi-code/CHANGELOG.md - #125

Merged
liruifengv merged 1 commit into
mainfrom
docs/sync-changelog-0.4.0
May 27, 2026
Merged

docs(changelog): sync 0.4.0 from apps/kimi-code/CHANGELOG.md#125
liruifengv merged 1 commit into
mainfrom
docs/sync-changelog-0.4.0

Conversation

@liruifengv

Copy link
Copy Markdown
Collaborator

Related Issue

No linked issue — this is a post-release docs sync. See the next section.

Problem

@moonshot-ai/kimi-code@0.4.0 has shipped to npm, but the docs site (docs/en/release-notes/changelog.md and docs/zh/release-notes/changelog.md) still stops at 0.3.0. Users browsing the changelog page do not see the new release.

What changed

Synced the new 0.4.0 block from apps/kimi-code/CHANGELOG.md into the docs-site changelog for both locales, following .agents/skills/sync-changelog/SKILL.md.

For each upstream entry I stripped the PR link and commit-hash decoration, then classified by the commit prefix (feat: → Features, fix: → Bug Fixes, refactor: → Refactors). The kimi export manifest enhancement was placed under Other because it is a behind-the-scenes manifest tweak rather than a primary user-visible feature.

The Chinese page mirrors the English page 1:1 on versions, sections, section order, and entry counts. Translation follows the glossary and typography rules in docs/AGENTS.md (TUI终端界面, subagent子 Agent, Thinking kept as a proper noun, full-width punctuation, spaces between Chinese and English, plugin / MCP server / manifest left in English to match docs/zh/customization/plugins.md). The [#1](issue link) artifact that changesets accidentally injected inside the paste-marker code span was stripped so the example reads as the intended literal [paste #1 +15 lines].

Verified with npm run build inside docs/ — the VitePress build completes cleanly. Section sets and entry counts between EN and ZH were script-checked to match.

Upstream apps/kimi-code/CHANGELOG.md is unchanged; per the skill, docs sync does not produce a changeset.

Checklist

  • I have read the CONTRIBUTING document.
  • I have linked a related issue, or explained the problem above.
  • I have added tests that prove my feature works. (N/A — docs-only change.)
  • Ran gen-changesets skill, or this PR needs no changeset. (Docs-sync PRs do not enter the changeset bundle, per sync-changelog skill.)
  • Ran gen-docs skill, or this PR needs no doc update. (This PR is the doc update.)

@changeset-bot

changeset-bot Bot commented May 27, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: f82c198

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new

pkg-pr-new Bot commented May 27, 2026

Copy link
Copy Markdown
pnpm dlx https://pkg.pr.new/@moonshot-ai/kimi-code@f82c198
npx https://pkg.pr.new/@moonshot-ai/kimi-code@f82c198

commit: f82c198

@liruifengv
liruifengv merged commit 16e881e into main May 27, 2026
7 checks passed
@liruifengv
liruifengv deleted the docs/sync-changelog-0.4.0 branch May 27, 2026 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant