bug: Version number jumped from 0.43.1 to 2.0.0, skipping 1.x entirely

[ayu-exorcist]

What version of Kimi Code is running?

@moonshot-ai/kimi-code@2.0.0

Which open platform/subscription were you using?

N/A - This is about version numbering, not runtime behavior

Which model were you using?

N/A

What platform is your computer?

N/A - This is a versioning question applicable to all platforms

What issue are you seeing?

The version number jumped from 0.43.1 directly to 2.0.0, completely skipping the 1.x series. This appears inconsistent with semantic versioning conventions.

From the releases page:

• Last 0.x version: @moonshot-ai/kimi-code@0.43.1
• Next version: @moonshot-ai/kimi-code@2.0.0 ⚠️

According to semantic versioning:

• A major bump from 0.43.1 should result in 1.0.0, not 2.0.0
• To reach 2.0.0, there should have been a 1.0.0 release first

The 2.0.0 release was triggered by PR #3849, which added the /desktop command with a changeset marked as major. However:

1. The change itself (adding a command) doesn't appear to be a breaking change
2. The version calculation seems incorrect (should be 1.0.0, not 2.0.0)
3. Kimi Code Desktop is at version 1.0.0, but CLI jumped to 2.0.0

What steps can reproduce the bug?

1. Check the releases page: https://github.com/MoonshotAI/kimi-code/releases
2. Observe version sequence: 0.43.1 → 2.0.0
3. Check PR feat(cli): add /desktop slash command and kimi install-app subcommand #3849 changeset file that triggered the major bump
4. Note that no 1.x version exists

What is the expected behavior?

According to semantic versioning:

• If this was meant to be a major version bump: 0.43.1 → 1.0.0
• If two major bumps occurred: 0.43.1 → 1.0.0 → 2.0.0 (with a 1.0.0 release)
• If this was intentional: Clear documentation explaining the version strategy

Additional information

Questions:

1. Was the jump to 2.0.0 intentional, or is this a versioning configuration issue?
2. If intentional, what's the reasoning for skipping 1.x entirely?
3. Is there a version alignment strategy between CLI (2.0.0) and Desktop (1.0.0)?

Investigation done:

• Reviewed 2.0.0 release notes - no explanation provided
• Reviewed PR #3849 - changeset marked as major
• Reviewed PR #3797 - automated release PR

This may be a configuration issue in .changeset/config.json or an intentional product decision that needs documentation.

Contribution

• I am willing to submit a PR for this bug fix myself (please wait for maintainer approval in this issue first)

[xuruizhe891-create]

因为1.x系列版本号由旧版kimi cli占用