11/13 Release Announcement

What is changing
Bug fixes
Fixed a bug with flox activate where environments were not being activated into your current shell, for example via . <(flox activate).
Removed NIX_REMOTE setting: previously, this was set to daemon. This resolves a bug with installing on WSL.

Active environments are now listed in your shell prompt.
When in a non-interactive context, the flox activate command will no longer throw an error when attempting to activate an environment that is already active.
Added support for the verbose flag for flox activate.
flox publish: we were previously always building from the stable branch. The publish command now builds the package with the requested nixpkgs stability.

What you need to do
Upgrade to the latest version of flox


Thanks for the update!

Would it be possible to write in the install doc what is the latest version of flox, in order to know if an upgrade is necessary?

Hi @etorreborre !
Yes, we are looking for better ways to tell users there is an updated flox version available. Because it currently would be a manual process to update the install docs for each update and we are updating flox quite frequently, we would like to provide a more automated method for updating users. For example, being notified of an update while using flox.
I suspect you will hear something soon on this front within the next couple weeks if not sooner.
Thanks for your feedback!

1 Like

Just to round off this thread, our future offerings will provide configurable options for selecting update notification methods and auto-update settings, but for today the most authoritative method would be to use flox!

$ flox search -c flox flox
$ flox install flox.flox
$ flox upgrade flox.flox

Or, if you have already upgraded to 0.0.7 or later then you can also flox pull either or both of our new flox/default and flox/prerelease flox-curated environments. More on that later as we work to update the automation and documentation around that process!

1 Like