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

Patch Changes

• #934 c5b6103 Thanks @tt-a1i! - Allow ACP sessions to start with configured non-OAuth model credentials instead of requiring terminal login.

• #1967 ad8cc85 Thanks @sailist! - Run web servers foreground-only end to end: the /web slash command now always starts a new server, and the kimi web kill / kimi web ps subcommands are removed — foreground servers stop with Ctrl+C. kimi server kill remains as a deprecated fallback that only stops servers started by a version before 0.28.0.

• #1948 f6f4192 Thanks @sailist! - Fix running subagents not observing permission mode switches made after they started.

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

Patch Changes

• #1888 5ae60fa Thanks @sailist! - Add a unified, agent-granular transcript rendering data layer and serve it from the v2 server: clients can fetch turn-paginated transcripts via GET /sessions/{id}/transcript and subscribe to per-agent transcript updates over the v1 WebSocket with per-connection granularity control (off / turn / block / delta). All transcript wire types are owned by the transcript package itself. turn.started now carries the turn's prompt text so live transcripts render the user input as soon as the turn opens.

@moonshot-ai/kap-server@0.0.2

Patch Changes

• #1888 5ae60fa Thanks @sailist! - Add a unified, agent-granular transcript rendering data layer and serve it from the v2 server: clients can fetch turn-paginated transcripts via GET /sessions/{id}/transcript and subscribe to per-agent transcript updates over the v1 WebSocket with per-connection granularity control (off / turn / block / delta). All transcript wire types are owned by the transcript package itself. turn.started now carries the turn's prompt text so live transcripts render the user input as soon as the turn opens.

• Updated dependencies [5ae60fa]:

  • @moonshot-ai/transcript@0.0.1
  • @moonshot-ai/agent-core-v2@0.1.2

@moonshot-ai/transcript@0.0.1

Patch Changes

• #1888 5ae60fa Thanks @sailist! - Add a unified, agent-granular transcript rendering data layer and serve it from the v2 server: clients can fetch turn-paginated transcripts via GET /sessions/{id}/transcript and subscribe to per-agent transcript updates over the v1 WebSocket with per-connection granularity control (off / turn / block / delta). All transcript wire types are owned by the transcript package itself. turn.started now carries the turn's prompt text so live transcripts render the user input as soon as the turn opens.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ad2006db53

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Include the public CLI in this release

When this release PR is merged, it consumes the only pending changeset while bumping only private packages (@moonshot-ai/kap-server, @moonshot-ai/agent-core-v2, and @moonshot-ai/transcript all have private: true); Changesets documents that private packages are only versioned/changeloged by default and private: true prevents npm publishing (https://github.com/changesets/changesets/blob/main/docs/config-file-options.md#privatepackages-object-or-false), and the repo's release workflow only produces Kimi native assets when @moonshot-ai/kimi-code is in publishedPackages. Since apps/kimi-code is the public package that bundles this server code, this would delete the transcript changeset without publishing a CLI/npm release containing the new endpoint.

Useful? React with 👍 / 👎.