ci: release packages#2061
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
July 23, 2026 04:36
1d4ca4b to
cc584a4
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 23, 2026 04:43
cc584a4 to
3ce6d1b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
527d485Thanks @7Sageer! - Add global default MCP server timeouts inconfig.tomland env vars.#2021
64f053cThanks @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.#2021
64f053cThanks @sailist! - Add a session API endpoint that returns all turn-opening user messages of a session, grouped per agent. QueryGET /api/v1/sessions/{session_id}/transcript/user-messages(optionally with?agent_id=for a single agent) to fetch them.Patch Changes
#2017
c6291c3Thanks @sailist! - Alignkimi -pon 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
188c0fcThanks @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
64f053cThanks @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.#2089
ca38b7eThanks @liruifengv! - Remove the toolbar tip that suggested trying the "superpowers" plugin.#2021
64f053cThanks @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.#2021
64f053cThanks @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).