fix(vscode): correct changeset package name - #11162
Merged
Merged
Conversation
imanolmzd-svg
enabled auto-merge (squash)
June 12, 2026 12:55
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge The fix is correct — Files Reviewed (1 file)
Reviewed by claude-4.6-sonnet-20260217 · 302,008 tokens Review guidance: REVIEW.md from base branch |
marius-kilocode
approved these changes
Jun 12, 2026
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
2 participants
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.
Summary
The
terminal-integrated-fontchangeset referenced the VS Code package by its directory name,kilo-vscode, instead of its workspace package name,kilo-code. This caused the v7.3.43 pre-release publish job to fail duringchangeset version; correcting the name allows the release workflow to consume the changeset.