fix(update): refresh kit on every kai update path#38
Merged
Conversation
kit versions on its own line (kai-tui), so a current launcher says nothing about kit's freshness — but runUpdate early-returned at 'Already on the latest version' before ever reaching the kit refresh at the bottom of the function. A user with a stale kit ran kai update, was told everything was current, and kept the old kit (2026-07-14 fresh-install dogfood, one release behind). Extract refreshKit() and call it on both paths.
🔍 Kai reviewTip Intent verified — does what the PR describes, nothing flagged.
+20 −6 · 1 file · reaches 0 View finding → · Awaiting your verdict — Kai never approves its own finding. |
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
1 participant
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.
kai update early-returned at "Already on the latest version (0.35.1)" — checked against kai-cli's release line only — and never reached the kit refresh at the bottom of runUpdate. Since kit versions independently (kai-tui line), a user with a current launcher and a stale kit was told everything was up to date. Observed on a fresh install today: launcher 0.35.1, kit stuck at 0.33.135 with 0.33.136 published.
refreshKit() extracted and called on both paths (already-latest and post-download). Best-effort as before: kit failure warns, never fails the launcher update.
🤖 Generated with Claude Code