Flox 1.18.1 is released!

Announcements
1

Flox Release 1.18.1

We held the 1.18.0 announcement while we tracked down a deactivation bug, so this one covers both releases.

Features

New in 1.18.0

  • Setting options.activate.upgrade-notifications = false in a manifest turns off upgrade notifications for everyone who activates that environment (needs schema-version = "1.18.0").

  • flox edit now upgrades a manifest to the lowest schema version that supports the fields you used, and prints a notice, instead of failing.

  • The Flox container image is published to Docker Hub as flox/flox.

1.18.0 also changed how flox build, flox develop and flox publish resolve nixpkgs, and flox publish now asks before replacing a package’s registered source.

Fixed in 1.18.1

  • Deactivating an environment you activated in your current shell no longer prints profile-scripts-deactivate is not expected in this context. Your [profile.deactivate] scripts run again, and activating the same environment again in the same shell sources its [profile] scripts again. Restart any active shell sessions to pick up the fixed prompt hook.

Heads-up: commands that resolve packages from the Flox Catalog will require a free FloxHub account in an upcoming release. 1.18.1 does not require it.

  • You can get ahead of it with flox auth login, or set FLOX_FLOXHUB_TOKEN in CI.

  • install-flox-action now has a floxhub-token field that allows authenticating with a service account token or personal access token.

  • Searching for packages and activating already-locked environments will keep working without signing in.

Details Here

Full release notes: v1.18.0 and v1.18.1

Download Links

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

1 Like