Download Latest Version v1.19.3 source code.zip (7.1 MB) Google Add to Preferred Sources
Home / v1.19.0
Name Modified Size InfoDownloads / Week
Parent folder
README.md 2026-10-20 3.0 kB
v1.19.0 source code.tar.gz 2026-10-20 6.3 MB
v1.19.0 source code.zip 2026-10-20 7.0 MB
Totals: 3 Items   13.4 MB 0

Warning

  • ⚠️ Starting October 20, 2026, you need to be logged in to a free FloxHub account to install packages, upgrade them, or do anything else that resolves packages from the Flox Catalog. We timed the change to land with this release, but the Flox Catalog enforces it, so it applies to every Flox version and not just 1.19.0. Run flox auth login, or set FLOX_FLOXHUB_TOKEN in CI. Searching for packages and activating an environment whose lockfile is up to date stay public. Logging in works on Flox 1.3.5 and newer, and tokens need 1.14.0 or newer. Details: https://go.flox.dev/auth

Features

  • Package groups can resolve against a specific catalog stability, set per group with pkg-groups.<NAME>.stability or for all groups with options.stability. This introduces manifest schema version 1.19.0.
  • flox list --all shows an environment-detail block with generation and sync information, per-package upgrade availability and stability, an available-upgrades summary, and next-step hints, all without making network requests.
  • flox build, flox publish and flox develop list the available packages when the named package doesn't exist, and flox publish and flox develop prompt for a package when there are several and none is named, or list them when not running interactively.
  • flox activate and flox run prompt you to run flox auth login, or to log in again when a login has expired, if downloading a custom-catalog package requires FloxHub authentication, instead of reporting that the package may have been deleted.
  • flox search and flox services status align their tabular output more consistently.

Fixes

  • flox run asks you to log in before showing the package picker, rather than after you've made a choice, when several packages provide the command and you are not logged in.
  • flox install, uninstall, edit and upgrade work in Docker and podman when the environment came from an earlier image layer.

Thank you to our community contributions this release

  • Concurrent activations of the same environment no longer fail because of a race on the activation lock file (@fzakaria)

[!NOTE] You can find the SHA256 checksums for Flox 1.19.0 and SHA512 checksums for Flox 1.19.0 online.

Source: README.md, updated 2026-10-20