chore(vscode): release 0.6.1 - #1783
Conversation
![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: 443418283c
ℹ️ 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".
| "displayName": "Kimi Code", | ||
| "description": "Official Kimi Code plugin for VS Code", | ||
| "version": "0.6.0", | ||
| "version": "0.6.1", |
There was a problem hiding this comment.
When this manifest is packaged as a 0.6.1 VSIX, the CI vscode-vsix-package job runs pnpm --filter kimi-code run test:extension-host, but that harness still asserts extension.packageJSON.version is exactly 0.6.0 in apps/vscode/test/extension-host/index.cjs:34. Because vsix-package.mjs builds and packages this updated manifest, the installed Extension Host smoke will fail before activation; the root test shard also still checks the User-Agent against kimi-code-vscode/0.6.0 in apps/vscode/test/kimi-harness.integration.test.ts:342. Please update these version-coupled tests or make them read the package version.
Useful? React with 👍 / 👎.
commit: |
|
* chore(vscode): release 0.6.1 * test(vscode): read the extension version from the manifest in version assertions * test(vscode): declare version on the runtime rig type
1 participant
Related Issue
None — release housekeeping for the VS Code extension.
Problem
The 0.6.0 extension shipped with a settings (gear) menu whose Sign in action did nothing when signed out. The fix already landed on
mainin #1779; we need to publish it as 0.6.1.What changed
apps/vscode/package.json(the version vsce publishes is read from this field).apps/vscode/CHANGELOG.md, which is packaged into the VSIX and shown on the marketplace page.The extension version is managed manually (it is not part of the changesets flow), so this PR is intentionally a two-file diff.
Checklist
gen-changesetsskill, or this PR needs no changeset. → Needs none: the VS Code extension (apps/vscode, private packagekimi-code) is versioned manually and is excluded from the changesets publish flow.gen-docsskill, or this PR needs no doc update. → No user-doc change: the changelog entry itself is the release note.