fix(cli): resolve curl upgrade version from npm dist-tag instead of GitHub releases/latest - #12167
Merged
Conversation
…itHub releases/latest
marius-kilocode
enabled auto-merge
July 13, 2026 10:40
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (3 files)
Previous Review Summary (commit 988a92e)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 988a92e)Status: 2 Issues Found | Recommendation: Address before merge Overview
Fix these issues in Kilo Cloud Issue Details (click to expand)WARNING
Files Reviewed (4 files)
Reviewed by gpt-5.6-sol · Input: 49.1K · Output: 8.6K · Cached: 452.8K |
chrarnoldus
approved these changes
Jul 13, 2026
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
fix(cli): resolve curl upgrade version from npm dist-tag instead of GitHub releases/latest
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
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.
Problem
kilo upgradefor curl-detected installs (~/.kilo/bin/kilo) resolved the latest version from GitHub's/releases/latestendpoint. That endpoint now returns JetBrains plugin releases (e.g.jetbrains/v7.0.4) instead of the latest CLI release, because JetBrains releases are published more recently than CLI releases. The old code stripped the leadingvfromtag_name, leavingjetbrains/v7.0.4— not a valid semver — which then broke the upgrade flow. This is the same root cause as issue #12125 (fixed for the install script in #12148), but in a separate code path:Installation.latest()insrc/installation/index.ts.Reported in Discord:
kilo upgradeandcurl https://kilo.ai/cli/installboth broken, withkilo --versionandkilocode --versiondiverging (stale curl-installed binary vs up-to-date npm-installed one).Fix
The curl/unknown fallback in
Installation.latest()now fetches the npmlatestdist-tag (${registry}/@kilocode%2fcli/${InstallationChannel}) instead of GitHub/releases/latest. This naturally excludes JetBrains releases and CLI prerelease channels (RC lives on thercdist-tag) without requiringjqor pagination. The npm branch already used this approach for npm/yarn/bun/pnpm installs — the curl fallback now uses the same source for consistency.upgradeCurlneeded no change: it passesVERSION: targetto the install script (already fixed in #12148), which constructs the versioned GitHub asset URL from it.Verification
Installation.latest("curl")withKILO_CHANNEL=latestresolves7.4.5from the live npm registrylatestdist-tag:7.4.5; npmrcdist-tag:7.4.2(prerelease correctly excluded)/releases/latest: still returnsjetbrains/v7.0.4(broken)test/kilocode/installation/upgrade.test.ts)