# 11/13 Release Announcement

**URL:** <https://discourse.flox.dev/t/11-13-release-announcement/491>\
**Category:** Announcements\
**Created:** [November 13, 2022, 6:53pm UTC](https://discourse.flox.dev/t/11-13-release-announcement/491 "2022-11-13T18:53:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jurraca](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/jurraca/32/397_2.png) [@jurraca](https://discourse.flox.dev/u/jurraca)\
**Post date:** [November 13, 2022, 6:53pm UTC](https://discourse.flox.dev/t/11-13-release-announcement/491/1 "2022-11-13T18:53:49Z")

</div>

_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.

**Improvements**  
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](https://beta.floxdev.com/docs/managing-flox/user_update/) of flox

---

<div class="post-metadata">

**Author:** ![etorreborre](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/etorreborre/32/428_2.png) [@etorreborre](https://discourse.flox.dev/u/etorreborre)\
**Post date:** [November 18, 2022, 9:35am UTC](https://discourse.flox.dev/t/11-13-release-announcement/491/2 "2022-11-18T09:35:15Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![robinbrantley](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/robinbrantley/32/39_2.png) [@robinbrantley](https://discourse.flox.dev/u/robinbrantley)\
**Post date:** [November 18, 2022, 2:51pm UTC](https://discourse.flox.dev/t/11-13-release-announcement/491/3 "2022-11-18T14:51:02Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![limeytexan](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/limeytexan/32/10_2.png) [@limeytexan](https://discourse.flox.dev/u/limeytexan)\
**Post date:** [December 2, 2022, 2:24pm UTC](https://discourse.flox.dev/t/11-13-release-announcement/491/4 "2022-12-02T14:24:29Z")

</div>

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!

```auto
$ flox search -c flox flox
flox.flox
  stable.flox.flox@0.0.6-r58
  stable.flox.flox@0.0.7-r76
$ 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!