opensource/kilocode
3
0
Fork 0
mirror of https://github.com/Kilo-Org/kilocode.git synced 2026-08-28 11:05:31 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat(jetbrains): publish bundled CLI builds

Browse Source
This commit is contained in:
kirillk
2026-07-24 12:49:58 -04:00
parent 232d7f2c61
commit 452d0eb55f
15 changed files with 691 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/kilo-jetbrains/RELEASING.md
+10
View File
@@ -132,6 +132,16 @@ Publishing behavior:
The workflow checks out `jetbrains/v<version>` for verification, signing, and Marketplace publishing. It overlays the reviewed `packages/kilo-jetbrains/gradle.properties` and `packages/kilo-jetbrains/CHANGELOG.md` from the merged PR before rendering release notes and before `publishPlugin`, so the Marketplace plugin version, Marketplace notes, and GitHub Release use the reviewed metadata.
After Marketplace publishing succeeds, `publish-jetbrains` dispatches `bundle-jetbrains`. The bundled workflow rebuilds the same `jetbrains/v<version>` tag with `-Pkilo.cli.bundled=true`, signs and verifies the all-platform plugin ZIP, then uploads `kilo-code-<version>-bundled.zip` to the same GitHub Release. Bundled builds keep `kilo.cli.pinned=true`; the build flag only embeds the pinned CLI release assets so runtime extracts the bundled current-platform CLI instead of downloading it.
Stable bundled releases also publish the GitHub Pages custom plugin repository XML:
```text
https://kilo-org.github.io/kilocode/jetbrains/updatePlugins.xml
```
RC bundled ZIPs are attached to prereleases for install-from-disk testing, but they do not update the stable custom repository XML.
## Installing RC Builds
RC builds are published to the `eap` channel. To get them in IntelliJ IDEA: