Skip to content

fix(installer): keep kivalup aligned with installed release - #84

Merged
zerosnacks merged 1 commit into
masterfrom
fix/kivalup-release-bundle
Sep 18, 2026
Merged

zerosnacks merged 1 commit into
masterfrom
fix/kivalup-release-bundle

Conversation

@zerosnacks

Copy link
Copy Markdown
Member

Summary

Treat kival, kivald, and kivalup as a single versioned release bundle.

kivalup is distributed alongside every Kival release, so there is no useful state where the installer should remain on a different release from the binaries it installs.

Changes

  • always install the release-provided kivalup
  • include kivalup in the installed-release check
  • refresh kivalup when it is missing or does not match the selected release
  • make explicit --install <version> installs include the corresponding installer
  • remove the separate refresh_kivalup path

Bare kivalup and kivalup --update continue to select the latest release; --update remains a user-facing alias rather than a distinct installation mode.

Treat kival, kivald, and kivalup as a single release bundle.

Always install the release-bound kivalup alongside the selected Kival
version, including explicit --install targets, and include kivalup in the
already-installed check so a stale or missing installer is refreshed.
@zerosnacks
zerosnacks enabled auto-merge (squash) September 18, 2026 12:57
@zerosnacks
zerosnacks merged commit ba2b398 into master Sep 18, 2026
11 checks passed
@zerosnacks
zerosnacks deleted the fix/kivalup-release-bundle branch September 18, 2026 13:01
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.

1 participant