chore: drop changesets merged with the klient facade (#1768) - #1775
Conversation
The klient facade PR landed with its release notes planned for a later feature release; removing the two pending changesets so the next release does not pick up version bumps and changelog entries for it.
|
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: 092bb7b9c7
ℹ️ 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 +0,0 @@ | |||
| --- | |||
| "@moonshot-ai/kap-server": minor | |||
| "@moonshot-ai/kimi-code": patch | |||
There was a problem hiding this comment.
With the existing pending @moonshot-ai/kimi-code patch changesets, the next release will still build the CLI from current main and bundle the already-merged kap-server v2 channel registrations. Removing this @moonshot-ai/kimi-code entry only drops the release note for that API; it does not defer the models/modelCatalog RPC surface, so the feature can ship in the next CLI release unannounced. If the intent is to hold it for a later feature release, gate or revert the channel registration instead of deleting the app changeset.
Useful? React with 👍 / 👎.
MoonshotAI#1775) The klient facade PR landed with its release notes planned for a later feature release; removing the two pending changesets so the next release does not pick up version bumps and changelog entries for it.
1 participant
Related Issue
Follow-up to #1768 (merged inadvertently with its release changesets).
Problem
#1768 landed with two pending changesets (
klient-global-facade-catalog.mdbumping@moonshot-ai/klientminor, andkap-server-v2-model-channels.mdbumping@moonshot-ai/kap-serverminor +@moonshot-ai/kimi-codepatch). The klient facade is meant to ship in a later feature release, so the next automated release must not pick up version bumps and changelog entries for it now.What changed
.changeset/klient-global-facade-catalog.md..changeset/kap-server-v2-model-channels.md.No code changes — the feature itself stays on
mainas merged in #1768.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.