Release v1.18.0 · flox/flox

Features

Setting options.activate.upgrade-notifications = false in a manifest (with schema-version = "1.18.0") turns off upgrade notifications for everyone who activates that environment.
flox edit upgrades a manifest to the lowest schema version that supports the fields it uses and prints a notice, instead of failing.
The Flox container image is now published to Docker Hub as flox/flox.

Starting with the next release, commands that resolve packages from the Flox Catalog will require a free FloxHub account. Run flox auth login to get ready, or set FLOX_FLOXHUB_TOKEN in CI. You can still search for packages and activate already locked environments without signing in. See https://go.flox.dev/auth for details.
install-flox-action now has a floxhub-token input for signing in to CI with a service account token or a personal access token.
flox publish asks for confirmation before replacing a package's registered source repository or ref. Pass --allow-lineage-change to allow this in non-interactive use.
flox build, flox develop and flox publish build Nix expression packages against the catalog's current nixpkgs, or the one set by --stability, instead of the revision the environment is locked to. Pass --nixpkgs-url <url> to pin a revision without contacting the catalog.

Activating an environment from inside its own activation no longer corrupts variables that a hook extended without a separator, such as TMPDIR, and no longer adds duplicate entries to list variables such as PATH.
flox envs no longer lists the local cache checkouts that back remote environments as separate inactive entries.
flox build accepts a namespaced catalog package, such as owner/pkg, in a build's runtime-packages list.

Note