Note: This release includes changes to how package outputs are handled that may trigger automatic manifest migrations. Migrated manifests will require CLI version 1.10.0 or above. See the Changes section below for details.
Compatibility policy:
Starting with this release, the Flox CLI is schema-aware. It detects when modifications to an environment are backwards compatible, and automatically migrates manifests when changes aren’t backwards compatible. The version field has been replaced with a schema-version field. See the compatibility policy docs for details.
Features:
- Package outputs are now supported, allowing you to specify which package outputs to include in your environment using
flox install curl^binor by settingoutputsin the manifest. flox installandflox searchnow show hints when a package has additional package outputs available.- The “building from source” spinner now explains why a package is being built from source (e.g. marked as
unfreeor has no upstream build available).
Changes:
- Package installations now include only the default package outputs defined by the upstream Nix package. Previously, all package outputs were installed. Existing environments that relied on non-default package outputs will be automatically migrated to set
outputs = "all"for those packages in the manifest, preserving existing behavior. Note that migrated manifests will require CLI version 1.10.0 or above.
Fixes:
flox edit --syncandflox edit --resetnow work for FloxHub environments, previously failing with “Cannot sync local or remote environments.”flox activate -m devno longer incorrectly addscoreutilsbinaries to the path, fixing a regression from v1.9.0.- Bash completion now works for
flox activatepositional arguments, andflox activate -cno longer produces an eval error when tab-completing inside quotes. - Removed several unused internal
FLOX_*environment variables fromflox activate.
Thank you to our community contributions this release:
- Fix deprecated
hostPlatformNix warnings
Release notes and download links here!