ci: release packages#1868
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 18, 2026 15:35
a61062e to
c312fb9
Compare
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
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.
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.0
Minor Changes
4f3c724Thanks @wbxl2000! - Breaking:kimi weband the TUI/webcommand now run the server in the foreground by default instead of backgrounding a daemon — the command stays attached to the terminal until Ctrl+C instead of returning immediately. Pass--backgroundin scripts or launchers to keep the previous background behavior;kimi server runis unchanged. An already-running server is reused as-is across upgrades (a version mismatch is pointed out in the output); runkimi server killonce after upgrading to restart on the new version.Patch Changes
#1867
3086e47Thanks @RealKai42! - Rename the stale "afk" reference to "auto" in the built-in MCP config skill guidance.#1867
3086e47Thanks @RealKai42! - Correct the YOLO and Auto permission mode descriptions in CLI --help output and in the ACP session mode selector shown by IDE clients.#1867
3086e47Thanks @RealKai42! - web: Correct the YOLO and Auto permission mode descriptions in the slash command list and the mobile permission sheet.#1867
3086e47Thanks @RealKai42! - Fix the YOLO and Auto permission mode descriptions to match their actual behavior: YOLO auto-approves tool actions but the agent may still ask questions, while Auto is fully autonomous and never asks.#1867
3086e47Thanks @RealKai42! - Correct the YOLO mode notice shown when replaying a session: tool actions are auto-approved, but the agent may still ask questions.