ci: release packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@moonshot-ai/kimi-code@0.32.0

Minor Changes

• #2558 75395f6 Thanks @sailist! - Add the TurnStarted, UserPromptQueued, TaskStarted, and SessionHeartbeat hook events, enrich hook payloads with the session title and client type, include the model and profile in SessionStart, and report SessionEnd as archive when a session is archived instead of exited. Configure the new events under [[hooks]] in config.toml.

Patch Changes

• #2416 eaab2b6 Thanks @mangeshraut712! - Fall back to the built-in models.dev catalog snapshot when the public catalog is unreachable, so Known third-party provider import still works offline or in blocked networks.

• #2083 bfa0080 Thanks @StaR4y! - web: Fix dark-mode monochrome controls and align the chat composer corner radius with the design system.

• #2559 dfc55a5 Thanks @wbxl2000! - Render the "/login" already-logged-in confirmation in the success color instead of dim text, so the "Already logged in. Model configuration refreshed." message is clearly visible.

• #2572 6ba75a1 Thanks @sailist! - Rename the [loop_control] max_retries_per_step config key to max_attempts_per_step and max_steps_per_run to max_steps_per_turn: on the v2 engine the old keys no longer take effect and a startup warning prompts the rename in config.toml. The KIMI_LOOP_MAX_RETRIES_PER_STEP env var is likewise deprecated in favor of KIMI_LOOP_MAX_ATTEMPTS_PER_STEP but keeps working with a warning.

• #2562 071b6a5 Thanks @sailist! - Serve v1 message history from the server layer and drop the engine-side legacy message adapter; the /api/v1 message contract is unchanged.

• #2562 071b6a5 Thanks @sailist! - Assemble the session snapshot endpoint from the engine's services for both cold and live sessions, and remove the KIMI_SNAPSHOT_READER, KIMI_SNAPSHOT_TIMEOUT_MS, and KIMI_SNAPSHOT_CACHE_LIMIT environment knobs.

@moonshot-ai/agent-core-v2@0.3.1

Patch Changes

• #2562 071b6a5 Thanks @sailist! - Serve v1 message history from the server layer and drop the engine-side legacy message adapter; the /api/v1 message contract is unchanged.

@moonshot-ai/kap-server@0.2.1

Patch Changes

• #2572 6ba75a1 Thanks @sailist! - Add the global event.config.warning WebSocket event that pushes the current set of config warnings (deprecated config keys or environment variables in use) to every connection whenever it changes.

• #2417 e22479a Thanks @liruifengv! - Expose the effective experimental-flag map as experimental_flags on GET /api/v1/meta.

• #2562 071b6a5 Thanks @sailist! - Serve v1 message history from the server layer and drop the engine-side legacy message adapter; the /api/v1 message contract is unchanged.

• #2562 071b6a5 Thanks @sailist! - Assemble the session snapshot endpoint from the engine's services for both cold and live sessions, and remove the KIMI_SNAPSHOT_READER, KIMI_SNAPSHOT_TIMEOUT_MS, and KIMI_SNAPSHOT_CACHE_LIMIT environment knobs.

• Updated dependencies [071b6a5]:

  • @moonshot-ai/agent-core-v2@0.3.1

@moonshot-ai/kimi-code-sdk@0.15.1

Patch Changes

• #2567 98ef0f0 Thanks @7Sageer! - Fix v1 replay ignoring v2 profile.bind records, which made sessions resumed from CLI-created wires lose their tool allowlist and send requests without tools.