Release v1.0.5 · flox/flox

Notable features and fixes

This release addresses several bugs and adds new improvements, including:

✨ New flox envs command allows you to list all environments you have activated on your machine. For upgrading users: you'll need to activate each existing environment at least once after upgrading to show up on the flox envs list. (#1264)
flox activate has been improved to make way for, among other things, better support for additional shells! (#1299)
- As before, the manifest [hook.on-activate] script is invoked using bash shell but it is now 1. invoked only with the first flox activate invocation and 2. invoked before the [profile] scripts. The [hook.on-activate] is now able to start daemons which export process/socket information. This is a small breaking change if you wrote a hook.on-activate after version 1.0.2 when it was first released.
- Flox environments can be activated by invoking /path/to/environment/.flox/run/{sytem-type}/activate directly.
- flox activate will default to using your $SHELL variable to detect the shell to be invoked in the "interactive" mode. You can set $FLOX_SHELL to override this behavior.
flox init can now detect Python projects with unconventional requirements.txt names following this pattern: requirements*.txt.(#1336)
Resolve an error with flox init -d where the final part of the path is a . or ... (#1425)
flox pull now has spinners and a message. (#1337) 🤓
flox show results are listed vertically. Deprecated unused --all option. (#1444)

crsche - feat(PyProject::detect): detect unconventional requirements.txt. (#1336)