Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
README.md | 2025-08-19 | 2.2 kB | |
v1.7.1 source code.tar.gz | 2025-08-19 | 3.7 MB | |
v1.7.1 source code.zip | 2025-08-19 | 4.1 MB | |
Totals: 3 Items | 7.8 MB | 0 |
Features
This release introduces a suite of flox generations
commands, which allows lightweight version control of environments that are pushed to FloxHub. Every change to a FloxHub environment creates a new generation. Changes can be very quickly undone with flox generations rollback
or you can choose a specific generation with flox generations switch
. To learn more, consult the documentation at https://flox.dev/docs/concepts/generations/
Unfortunately, due to an unavoidable schema change, FloxHub environments that are created or modified with Flox >= v1.7.0 will no longer be usable with older versions of Flox. Other users of that environment will need to upgrade Flox if they receive the following error:
Invalid version at line 1 column 12
Improvements
- The
flox activate
command now cacheszsh
completions in$FLOX_ENV_CACHE/.zcompdump
to speed up the repeat activation of environments. The cache is rebuilt when environments are activated in a different order or combination, which can be debugged withflox activate -v
. - Fixed a bug in
flox init --auto-setup
for Yarn projects that now ensures a compatible version of NodeJS will be installed. - Fixed a bug with the handling of invalid characters (e.g.
=
) in package paths. - Fixed a compatibility bug that was introduced in Flox v1.5.0 which caused environments that were locked with much older Flox v1.3.x versions to no longer build.
Note: Flox v1.7.0 contained an installation bug that caused failures with install-flox-action
. This was caught during release testing, and v1.7.0 was never announced.