chore: rewrite pending changesets for the new changelog conventions - #3026
Conversation
🦋 Changeset detectedLatest commit: 2a5f9c0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@codex review |
bj456736
changed the title
commit: |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8acd1fa26c
ℹ️ 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".
| @@ -1,6 +1,5 @@ | |||
| --- | |||
| "@moonshot-ai/kimi-code": patch | |||
There was a problem hiding this comment.
The SDK change in 98ebda8 is not merely an internal read: it adds the public Session.getTodos() method and exports SessionTodoItem and SessionTodoStatus. Removing the SDK entry leaves that API addition absent from the generated SDK changelog; add a separate @moonshot-ai/kimi-code-sdk changeset with SDK-specific wording rather than dropping the package entirely.
Useful? React with 👍 / 👎.
| "kimi-code": patch | ||
| --- | ||
|
|
||
| Show plugin- and file-declared MCP servers in the MCP servers panel as read-only entries instead of offering to edit or delete them. |
There was a problem hiding this comment.
This release note incorrectly classifies every file-declared server as read-only. McpServerRegistry.list() marks user-level mcp.json entries as mutable: true; only project-layer file entries and plugin entries lose the edit/delete controls. As written, users may expect their normal user-level servers to become read-only, so identify these as project-declared servers instead.
Useful? React with 👍 / 👎.
|
@codex review |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubCodex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
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". |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2a5f9c0a2e
ℹ️ 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".
| "@moonshot-ai/kimi-code-sdk": minor | ||
| --- | ||
|
|
||
| Unify the MCP management surface behind a source-tagged registry, covering plugin-declared servers in `listMcpServers` and adding `getMcpServer`, `testMcpServerConfig`, runtime `addMcpServer`, `inspectAppMcpServers`, and an `oauth-expired` auth state. |
There was a problem hiding this comment.
For SDK consumers using the v2 harness, this entry promises that listMcpServers covers plugin-declared servers, but SDKRpcClientV2 still exposes only its workspace connection manager and explicitly has no plugin MCP inventory; its app catalog likewise contains global entries only. Qualify this capability as legacy/v1-only so the SDK changelog does not advertise unsupported v2 behavior.
Useful? React with 👍 / 👎.
2 participants
Rewrites the pending
.changeset/entries to follow the new changelog conventions: one short user-facing English sentence per entry; no changesets for changes users cannot perceive; no entries for core/server-internal changes unless they fix a user-useful bug; new features state how to use them and experimental features state how to enable them; nomajor; internal-package changes that are user-perceivable in the CLI list only@moonshot-ai/kimi-code, and sdk/pi-tui list only themselves.Each entry was checked against the PR that introduced it (
gh api .../commits?path=).goal-objective-too-long-message.mdfix-gemini-thought-signature.mdagent-core-v2andkosong—node-sdkwas never changed, so the sdk line was spurious. Text is now one sentence.undo-todo-panel-revert.mdv1-mcp-management-plane.mdmedia-registrar-stale-alias.mdlazy-global-search-startup.mdpersist-token-counting-ledger.mdtoken_counting.*field names.goal-objective-length-warning.mdqueue-skill-commands-while-busy.mdclean-staged-media.mdstaging-leases): already one accurate user-facing sentence.fork-print-resume-command.mdfix-utf8-text-binary-detection.mdtower-slash-command.mdinline-multi-skill-tui.mdinlineSlashTrigger: truein the editor setup); the "opt-in" in the pi-tui entry is a pi-tui API-level editor option, not a user setting — CLI users need no enable step.web-title-flag.mdsdk-upload-file.mdinline-multi-skill-sdk.mddaemon-file-ref-drop-path.mdinline-slash-trigger-pi-tui.mdNotes on judgment calls:
"kimi-code"(VS Code extension) entry was kept as a separate file rather than deleted: PR feat(agent-core): unify the v1 MCP management plane #2858 did change the extension (MCPServersModal,mcp.handler) in a user-perceivable way — plugin- and file-declared MCP servers now show as read-only entries with an explanation instead of offering broken edit/delete actions.majoranywhere; no ignored packages (vis*,kimi-inspect) in any frontmatter.