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.30.0

Minor Changes

• #2065 527d485 Thanks @7Sageer! - Add global default MCP server timeouts in config.toml and env vars.

• #2021 64f053c Thanks @sailist! - Extend the transcript protocol with step usage and timing, streamed tool input and progress, subagent outcomes, agent status, and the prompt queue; WebSocket connections subscribed to the transcript protocol no longer receive the equivalent legacy session events.

• #2094 d751b67 Thanks @sailist! - Add a server endpoint to look up the plan content and review outcome of ExitPlanMode calls. Query GET /api/v1/sessions/{session_id}/transcript/plan with agent_id, plus an optional tool_call_id to narrow to one call.

• #2094 d751b67 Thanks @sailist! - Move transcript stream subscriptions on the server WebSocket protocol to a dedicated subscribe_v2 control frame paired with an agent-grained unsubscribe_v2; the transcript and transcript_since fields on client_hello and subscribe are no longer accepted.

• #2021 64f053c Thanks @sailist! - Add a session API endpoint that returns all turn-opening user messages of a session, grouped per agent. Query GET /api/v1/sessions/{session_id}/transcript/user-messages (optionally with ?agent_id= for a single agent) to fetch them.

• #2096 5fdbdb4 Thanks @7Sageer! - Add environment variables to configure the web search and web fetch services without OAuth login.

Patch Changes

• #2017 c6291c3 Thanks @sailist! - Align kimi -p on the experimental engine with the default engine's run lifecycle: the print background policy now defaults to steer with no practical turn or time cap, background task and per-turn step limits are lifted unless configured, and the run stays alive while cron tasks still have future fires so their steered turns can run.

• #2068 188c0fc Thanks @sailist! - Decouple provider and model management from config persistence on the experimental engine: the runtime keeps its own provider/model registry, and a dedicated sync layer hydrates it from config.toml at startup and writes runtime changes (added providers, discovered models, default-model selection) back to disk.

• #2021 64f053c Thanks @sailist! - Record plan content as versioned facts: each plan review submission offloads the document to a versioned per-agent plan directory and journals a reference record, so the transcript surfaces plan revisions (marker + badge with review path) and rebuilds them after restarts.

• #2104 66f611a Thanks @RealKai42! - Fix loss of thinking content with OpenAI-compatible endpoints that return reasoning under a different field name (e.g. newer vLLM); the reasoning field is now detected per endpoint and echoed back on follow-up requests.

• #2089 ca38b7e Thanks @liruifengv! - Remove the toolbar tip that suggested trying the "superpowers" plugin.

• #2094 d751b67 Thanks @sailist! - Push every session's work status (busy, pending interaction, last turn outcome) to all connected WebSocket clients without requiring a per-session subscription, and serve the same aggregate on the session list API.

• #2021 64f053c Thanks @sailist! - Stop embedding historical turns in the transcript WS baseline reset; it now carries only global state and the stream watermark, and clients page history through the REST transcript API.

• #2094 d751b67 Thanks @sailist! - Decouple the transcript WebSocket stream from the legacy agent filter: transcript frames are now governed by the per-agent transcript grades alone, so a connection no longer silently drops transcript data for agents missing from its event allowlist.

• #2021 64f053c Thanks @sailist! - Persist task lifecycle and interaction records in session wire journals, and rebuild tasks, interactions, todos, and goal/plan meta when loading a cold transcript, so transcript state survives server restarts (older sessions are unaffected).