Skip to content

v0.40.0

Choose a tag to compare

View all tags
@z3thon z3thon released this 11 Jun 02:43
· 7 commits to main since this release
v0.40.0
c0c6c3f

0.40.0 — Welcome to K2 by Alakazam Labs

K2SO is now K2. New name, new icon, new home — same product, and
everything you had is exactly where you left it.

What this update did on your machine (automatically):

  • Your app is now K2.app with the new K2 icon.
  • All workspaces, sessions, agents, schedules, settings, and your
    K2 Connect sign-in carried over. The daemon, heartbeat, and credential
    refresher re-registered themselves under their new names and
    reconnected on their own — if you can read this, it worked.
  • The CLI is now k2 (try k2 activity). Your existing k2so
    commands and scripts still work — k2so stays as an alias through
    the 0.x series, and prints a gentle reminder to switch.
  • Your data folder moved from ~/.k2so to ~/.k2, with a
    compatibility link left behind so older scripts keep working.
  • Updates now come from K2's new home:
    github.com/Alakazam-211/K2.

Licensing, as announced in 0.39.48: K2 is now Fair Source
(FSL-1.1-Apache-2.0). Free to use for individuals and businesses, source
visible, each version converts to Apache 2.0 after two years. Details:
LICENSE.md, COMMERCIAL_HOSTING_GRANT.md, and TRADEMARKS.md in the new
repository.

Thanks for riding along since the K2SO days. Onward.

Updating remote / headless macOS servers

The rename is a once-per-product-lifetime identity change, and most of it self-heals — but a few things on a macOS server need someone at the machine once:

Fully automatic (no hands needed): the update itself, the ~/.k2so → ~/.k2 data migration, launchd agent migration (dev.k2.daemon), daemon reconnection, and headless daemon-only installs (the standalone k2-daemon self-update has no prompts at all). The k2so CLI alias keeps working without any approval.

Needs one screen visit: macOS keys permissions to the app's bundle ID, and K2's is new (dev.k2.app). Re-grant Accessibility / microphone / notifications where the old app had them, approve the keychain access dialog if it appears on first K2 Connect use, and (optionally) approve the one-time admin prompt that puts the new k2 command on your PATH.

Every future update rides the new identity — this does not happen again.

Assets 9
Loading