chore: prune non-user-facing changesets before release - #2335
Merged
Conversation
- Drop changesets for changes users cannot perceive: internal bash parser groundwork, host-identity server start option, and the structured managed-usage refactor - Drop the duplicate agent-core-v2 repeat-breaker entry and remap the v1 fix to @moonshot-ai/kimi-code with user-facing wording - Remove the untouched @moonshot-ai/kimi-code-sdk entry from the quota-exhausted fail-fast changeset - Downgrade the upload size-cap removal to patch and drop the implementation detail from its wording
|
| Name | Type |
|---|---|
| @moonshot-ai/kimi-code | Minor |
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
No linked issue — this is release-hygiene cleanup of the accumulated
.changeset/entries, explained below.Problem
Several pending changesets don't belong in the user-facing CLI changelog per the
gen-changesetsrules:@moonshot-ai/kimi-code-sdkalthoughpackages/node-sdkwas not touched by the change.minorbump for removing an upload size limit, which is an improvement to an existing feature (patch).What changed
bash-parser-service.md,host-identity-system-prompt.md,structured-managed-usage.md— changes users cannot perceive.v2-dedup-register-rejected-calls.md— duplicate of the same repeat-breaker fix on the experimental engine; one CLI entry covers it.dedup-register-rejected-calls.md: remapped@moonshot-ai/agent-coreto@moonshot-ai/kimi-code(patch) and rewrote the entry in user-facing wording, so the fix is actually announced.quota-exhausted-fail-fast.md: dropped the@moonshot-ai/kimi-code-sdkline (node-sdk was not changed).upload-no-size-cap.md: downgradedminor→patchand removed the implementation-detail sentence.No code changes; deleting a changeset only removes its future changelog entry.
Checklist
gen-changesetsskill, or this PR needs no changeset. (This PR edits changesets themselves; no new changeset needed.)gen-docsskill, or this PR needs no doc update. (No behavior change.)