Skip to main content

Release Notes 1.5.1

Skulk 1.5.1 completes the first production desktop distribution path around the current stable main runtime. It does not promote the unreleased runtime work on dev and does not change Skulk's wire behavior from 1.5.0.

Highlights​

  • One version across every supported artifact. The signed and notarized Apple Silicon app, direct amd64 and arm64 Debian downloads, packages in the signed Foxlight APT repository, and the Homebrew cask all identify as Skulk 1.5.1 and embed the exact Skulk and desktop source revisions used to build them.

  • The macOS app has a stable update path. The menu-bar app checks Foxlight's canonical stable-release manifest and offers the signed DMG when a newer stable build is available. It does not silently replace the running app.

  • Linux installation is a normal package-manager journey. Installing the Foxlight archive keyring and running sudo apt install skulk installs the matching runtime and desktop controller. The public release gate repeats that journey in clean amd64 and arm64 environments, verifies embedded provenance, and never starts Skulk during qualification.

  • Desktop installation is the preferred user path. The apps retain the existing service, namespace, dashboard, and diagnostic controls while hiding implementation-level launchers from normal application discovery. Source installation remains available for contributors and advanced operators.

Upgrade notes​

  • Skulk runtime behavior is unchanged from 1.5.0. The product still requires every node in a cluster to run the same Skulk version, so update the complete cluster to 1.5.1 before serving workloads.
  • Existing macOS 1.5.0 installations do not contain the new update notifier; install 1.5.1 once through the DMG or Homebrew. Later stable releases can be discovered from inside the app.
  • The Linux packages do not start skulk.service during installation. Start Skulk deliberately from the desktop controller or the user service after applying the same persisted namespace to every node that should cluster.

The complete change inventory remains in the repository changelog.