chore: rewrite unreleased changesets per the gen-changesets rules - #3108
Conversation
🦋 Changeset detectedLatest commit: cde3bad The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@codex review |
commit: |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 05c0fd4127
ℹ️ 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".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 05f2ad5dda
ℹ️ 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".
|
@codex review |
|
Codex Review: Didn't find any major issues. What shall we delve into next? Reviewed commit: ℹ️ About Codex in GitHubCodex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
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". |
What
Rewrites the accumulated unreleased entries under
.changeset/to follow thegen-changesetsskill rules (one short user-facing sentence; no mechanism/cause clauses; skip changes users cannot perceive; one logical change per file). Requested by @liruifengv.No code changes — changeset files only.
Kept as-is (already compliant)
fix-tool-call-422-strict-providers.md— fix(kosong): emit null content for assistant messages with no text in chat completions #3052mcp-oauth-authenticate-tool.md— fix(agent-core-v2): register needs-auth MCP authenticate tool regardless of settle timing #3083Rewritten
file-write-staleness-guard.mdsubagent-delegation-cap.md*) → "Sub-agents no longer spawn their own sub-agents by default; custom agent profiles can still allow it explicitly."swift-views-scream.mdkimi-code= the vscode package, kept)tidy-media-tool-hints.mdwait-for-tool.mdminor, trimmed parameter/timeout mechanics → "Add the WaitFor tool: the agent can now wait for a background task to finish within the current turn instead of ending the turn and being re-invoked."Deleted (not perceivable by CLI users / duplicates)
subagent-spawned-task-id.md(fix(agent-core-v2): emit subagent.spawned after task registration #3005) — wire-protocol timing fix; the PR's own checklist states "no changeset: protocol plumbing not perceivable by CLI". The user-visible symptom it fixed (a dock row that cannot be stopped right after appearing) belongs to the app, which maintains its own changelog.transcript-live-attachments-goal-clear.md(feat: project prompt attachments into the live transcript and clear the transcript goal on clear #3088) — transcript projection plumbing for the app (live prompt attachments + goal clear), not perceivable in the CLI; it also bundled two logical changes in one file.wait-for-progress.md(feat(kimi-code): specialize the WaitFor tool's transcript display #3066) andwait-for-tui-display.md(feat(kimi-code): specialize the WaitFor tool's transcript display #3066) — WaitFor is itself a brand-new, unreleased tool; its transcript display ships with the first release, so there is no user-perceivable "improvement" beyond the new-tool entry inwait-for-tool.md.Checklist