Flox 1.17.0 is released!

Announcements
1

Flox Release 1.17.0

Features

  • flox develop [<package>] opens a development shell for a Nix expression build, with the package’s build inputs on PATH and the stdenv build phases loaded, so a failing build can be driven by hand without a full flox build. -c/--command runs a command in that shell instead of entering it, and the shell’s build inputs are protected from garbage collection while the shell is open.
  • The toplevel description manifest field is rendered as Markdown for interactive flox activate, and its first line is shown in flox envs. Requires schema-version = "1.17.0" in manifest.toml.
  • flox init -D creates a <current_user>/default environment on FloxHub, equivalent to flox init -r <current_user>/default, matching the existing -D shorthand on flox activate.
  • flox install includes a description explaining how to activate from shell RC files when it creates a new default FloxHub environment for a first-time user.

Changes

  • flox upgrade --dry-run no longer builds or downloads packages and only reports which packages have upgrades available. A successful --dry-run therefore no longer guarantees that the upgraded environment builds.

Fixes

  • flox auth status exits non-zero and prints a warning when your FloxHub token has expired, instead of reporting success with a past expiry date.
  • flox activate --start-services and the flox services commands recover automatically when a previous service manager was killed without cleaning up its socket. Previously the environment’s services stayed unusable until the socket file was deleted by hand.
  • flox prompts only once for access to the keychain instead of every release.
  • Catalog requests wait for the server-requested delay and retry when the service is temporarily unavailable.
  • flox config -l documents why it omits unset optional configuration values, including auto_activate.

Download Links

Note: You can find the SHA256 checksums for Flox 1.17.0 and SHA512 checksums for Flox 1.17.0 online.