Skip to content

fix(jetbrains): add missing vsix dependency for build pipeline#5747

Open
Githubguy132010 wants to merge 3 commits intoKilo-Org:mainfrom
Githubguy132010:fix/jetbrains-build-vsix-dependency
Open

fix(jetbrains): add missing vsix dependency for build pipeline#5747
Githubguy132010 wants to merge 3 commits intoKilo-Org:mainfrom
Githubguy132010:fix/jetbrains-build-vsix-dependency

Conversation

@Githubguy132010
Copy link
Contributor

Context

The JetBrains build GitHub Action was failing with error exit code 9 because the vsix:unpacked task couldn't find the VSIX file to unzip.

Implementation

The issue was in jetbrains/plugin/turbo.json where copy:kilocode and copy:resource-kilocode tasks depended on kilo-code#vsix:unpacked but not on kilo-code#vsix to create the VSIX file first.

The fix adds "kilo-code#vsix" as a dependency for both tasks:

  • copy:kilocode: now depends on ["clean:kilocode", "kilo-code#vsix", "kilo-code#vsix:unpacked"]
  • copy:resource-kilocode: now depends on ["clean:resource-kilocode", "kilo-code#vsix", "kilo-code#vsix:unpacked"]

This ensures the VSIX file is built (kilo-code#vsix../bin/kilo-code-*.vsix) before being unpacked (kilo-code#vsix:unpacked../bin-unpacked).

How to Test

Run the JetBrains build pipeline:

pnpm turbo jetbrains:build

The build should complete successfully without the "unzip: cannot find or open" error.

Get in Touch

The jetbrains build was failing because copy:kilocode and
copy:resource-kilocode tasks depended on vsix:unpacked but not
on vsix to create the VSIX file first.

This ensures the VSIX file is built before being unpacked.
@changeset-bot
Copy link

changeset-bot bot commented Feb 7, 2026

🦋 Changeset detected

Latest commit: 6dee958

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
kilo-code Patch

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

@chatgpt-codex-connector
Copy link

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@Githubguy132010
Copy link
Contributor Author

The GitHub Action failing is purely cosmetic as it's probably being run from main. Tested on my fork on this branch and check passed.

@adamhill
Copy link
Contributor

adamhill commented Feb 9, 2026

LGTM, tested artifact on IntelliJ, Rider, PHPStorm and PyCharm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants