chore(changesets): simplify pending CLI changelog entries - #2823
Merged
Conversation
|
| Name | Type |
|---|---|
| @moonshot-ai/kimi-code | Patch |
| @moonshot-ai/kimi-code-sdk | Patch |
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
commit: |
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
1 participant
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.
Related Issue
N/A — changelog wording maintenance before the pending release.
Problem
Several pending changesets for the next release (0.34.1) are long or describe internal mechanics instead of the user-visible effect. The open release PR (#2710) pre-generates
apps/kimi-code/CHANGELOG.mdfrom these changesets, and the docs-site changelog later inherits the same wording, so the text should be concise and user-facing before the release ships.What changed
Reworded five pending changesets to one short, user-facing sentence each; facts and bump levels are unchanged:
calm-mcp-auth-probe: drop the internal "reusing the connection-time check" phrasing; state the effect (OAuth servers detected withoutauth: "oauth"in the config)compaction-token-full-request-basis: drop the stat-composition detail; keep that counts now match the numbers shown during the sessionfix-tui-startup-freeze: trim redundant wordingisolate-session-profile-catalogs: replace internal jargon ("subagent tool projection") with the user-visible leakwindows-bare-command-binary-planting: collapse the two-sentence mechanism description into one sentence about the riskThe remaining pending CLI changesets (
fix-multi-select-other-deselect,fix-windows-missing-git-bash,steer-goal-turn-boundary) are already single short sentences and were left untouched, as was the SDK-onlyquiet-mcp-auth-status. Once this merges, the changesets action regenerates release PR #2710 with the new wording.Checklist
gen-changesetsskill, or this PR needs no changeset. (No changeset — this PR only edits pending changeset wording)gen-docsskill, or this PR needs no doc update. (No doc update — the docs changelog syncs post-release from the regenerated changelog)