ci: release packages - #390
Conversation
565c67e to
55c4d7b
Compare
![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: 55c4d7b63f
ℹ️ 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".
| "version": "0.8.1", | ||
| "private": true, |
There was a problem hiding this comment.
The changeset guide in .changeset/README.md says only @moonshot-ai/kimi-code and @moonshot-ai/kimi-code-sdk are publishable and explicitly lists @moonshot-ai/agent-core as a private internal package, so this release entry creates a @moonshot-ai/agent-core@0.8.1 changelog/version even though the npm release workflow will not publish that private package. Since the CLI changelog already captures the user-visible fix, please drop the agent-core version/changelog changes (or make the package publishable if that is now intended).
Useful? React with 👍 / 👎.
| "@moonshot-ai/agent-core": patch | ||
| "@moonshot-ai/kimi-code": patch |
There was a problem hiding this comment.
This changeset releases the CLI but not @moonshot-ai/kimi-code-sdk, even though SDK users get the same built-in Edit tool through SDKRpcClient constructing KimiCore and packages/node-sdk/tsdown.config.ts bundling @moonshot-ai/agent-core. In SDK sessions that hit the stale-file Edit error, npm consumers will therefore keep seeing the old message until the SDK is versioned as well, so include @moonshot-ai/kimi-code-sdk in this release instead of the private core package.
Useful? React with 👍 / 👎.
176c9b0 to
b1c05d0
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b1c05d050f
ℹ️ 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".
| { | ||
| "name": "@moonshot-ai/kimi-code-oauth", | ||
| "version": "0.2.1", | ||
| "version": "0.2.2", |
There was a problem hiding this comment.
The changeset guide lists @moonshot-ai/kimi-code-oauth under private internal packages and says only the CLI and SDK are publishable, so this version bump creates a 0.2.2 changelog/version for a package that the npm release will not publish. The OAuth fix is already represented through the publishable CLI/SDK artifacts that bundle it, so leaving this private package in the release metadata makes the release PR advertise a package release that cannot happen.
Useful? React with 👍 / 👎.
| "version": "0.7.1", | ||
| "private": true, |
There was a problem hiding this comment.
I checked the release workflow and it publishes with pnpm changeset publish; Changesets documents private: true as the way to prevent a package from being published. Fresh evidence after the earlier SDK-selection comment is that this release now bumps @moonshot-ai/kimi-code-sdk, but the same manifest still marks it private, so 0.7.1 will be versioned/changeloged while npm publishing skips it and SDK users will not receive the advertised OAuth fix.
Useful? React with 👍 / 👎.
b1c05d0 to
4bf6ca0
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4bf6ca0109
ℹ️ 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".
| { | ||
| "name": "@moonshot-ai/acp-adapter", | ||
| "version": "0.2.0", | ||
| "version": "0.2.1", |
There was a problem hiding this comment.
In the release workflow I checked, publishing is done via pnpm changeset publish (.github/workflows/release.yml:58), but this package is still marked private: true in its manifest, so npm will skip it even though this release PR now advertises @moonshot-ai/acp-adapter@0.2.1 and adds a changelog entry. Please remove this private-package version/changelog bump unless the adapter is actually being made publishable in the same release.
Useful? React with 👍 / 👎.
| { | ||
| "name": "@moonshot-ai/migration-legacy", | ||
| "version": "0.1.8", | ||
| "version": "0.1.9", |
There was a problem hiding this comment.
This release PR bumps @moonshot-ai/migration-legacy, but the same manifest still declares the package as private: true and the release workflow publishes with pnpm changeset publish (.github/workflows/release.yml:58), so this package will not be published despite the generated 0.1.9 release metadata. Please remove the private package from the release output, or make it publishable if that is intended.
Useful? React with 👍 / 👎.
3482639 to
fec84e9
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fec84e9bfb
ℹ️ 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".
| { | ||
| "name": "@moonshot-ai/kosong", | ||
| "version": "0.3.2", | ||
| "version": "0.3.3", |
There was a problem hiding this comment.
The release workflow publishes with pnpm changeset publish (.github/workflows/release.yml), and this manifest still marks @moonshot-ai/kosong as private: true, while .changeset/README.md lists it as an internal package that should not get release changesets. This version/changelog entry will advertise @moonshot-ai/kosong@0.3.3 even though npm publishing skips private packages; please remove this private-package bump and represent the provider fix through the affected publishable CLI/SDK artifacts instead.
Useful? React with 👍 / 👎.
140daa6 to
f16a3d6
Compare
f16a3d6 to
3bfca88
Compare
1 participant
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.10.0
Minor Changes
#433
85338e9- Add the built-inupdate-configskill — you can now have Kimi edit its own config files.#420
86a42a2- Add persistent experimental feature toggles and a TUI panel that applies confirmed changes by reloading the current session.#383
15d71b5- Add /reload to reload the current session and apply updated config files, plus /reload-tui to reload only TUI preferences.#393
beb12ac- Users now can prepare several goals for the agent to work on sequentially. The agent will pick up the next goal from the queue once the current goal is completed. Use/goal next <objective>to queue a goal and/goal next manageto review and change the queue interactively.#431
6a4e4c7- Add a doctor command for validating Kimi Code configuration files.Patch Changes
#393
beb12ac- Stop carrying active and queued goals into forked sessions.#408
6303bd2- Point session error diagnostics to the/export-debug-zipcommand.#398
b2801c4- Set terminal tab titles without renaming the running process.#403
d645d7e- Start automatic background updates as soon as startup's fresh update check finds a newer version.#387
6e74027- Lowercase the stale file content message in edit tool errors.#428
853c5fc- Ensure Nix-packaged CLI builds can find ripgrep and fd.#411
4598262- Normalize malformed Responses stream rate limit errors as provider rate limit failures.#405
07e2e0f- Refresh the update target before showing foreground update prompts so the displayed version matches the install.#399
232ed87- Keep managed OAuth credentials scoped to their configured authentication and API endpoints.#407
07609b4- Set the CLI process title to kimi-code during startup.#419
d0f8e24- Document the Git Bash prerequisite for Windows installs.#430
be0da5f- Fail early when Git Bash is missing on Windows before starting CLI sessions.@moonshot-ai/agent-core@0.9.0
Minor Changes
#433
85338e9- Add the built-inupdate-configskill — you can now have Kimi edit its own config files.#420
86a42a2- Add persistent experimental feature toggles and a TUI panel that applies confirmed changes by reloading the current session.#383
15d71b5- Add /reload to reload the current session and apply updated config files, plus /reload-tui to reload only TUI preferences.Patch Changes
#393
beb12ac- Stop carrying active and queued goals into forked sessions.#387
6e74027- Lowercase the stale file content message in edit tool errors.#399
232ed87- Keep managed OAuth credentials scoped to their configured authentication and API endpoints.#430
be0da5f- Fail early when Git Bash is missing on Windows before starting CLI sessions.Updated dependencies [
4598262]:@moonshot-ai/kimi-code-sdk@0.8.0
Minor Changes
#420
86a42a2- Add persistent experimental feature toggles and a TUI panel that applies confirmed changes by reloading the current session.#383
15d71b5- Add /reload to reload the current session and apply updated config files, plus /reload-tui to reload only TUI preferences.#431
6a4e4c7- Add a doctor command for validating Kimi Code configuration files.Patch Changes
#399
232ed87- Keep managed OAuth credentials scoped to their configured authentication and API endpoints.#430
be0da5f- Fail early when Git Bash is missing on Windows before starting CLI sessions.@moonshot-ai/acp-adapter@0.2.1
Patch Changes
85338e9,beb12ac,6e74027,86a42a2,15d71b5,232ed87,6a4e4c7,be0da5f]:@moonshot-ai/kosong@0.3.3
Patch Changes
4598262- Normalize malformed Responses stream rate limit errors as provider rate limit failures.@moonshot-ai/migration-legacy@0.1.9
Patch Changes
85338e9,beb12ac,6e74027,86a42a2,15d71b5,232ed87,be0da5f]:@moonshot-ai/kimi-code-oauth@0.2.2
Patch Changes
232ed87- Keep managed OAuth credentials scoped to their configured authentication and API endpoints.