# Release Announcement v0.1.4 (April 20 2023)

**URL:** <https://discourse.flox.dev/t/release-announcement-v0-1-4-april-20-2023/734>\
**Category:** Announcements\
**Created:** [April 20, 2023, 4:32pm UTC](https://discourse.flox.dev/t/release-announcement-v0-1-4-april-20-2023/734 "2023-04-20T16:32:07Z")\
**Posts on this page:** 8\
**Page:** 1

<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:** [April 20, 2023, 4:32pm UTC](https://discourse.flox.dev/t/release-announcement-v0-1-4-april-20-2023/734/1 "2023-04-20T16:32:07Z")

</div>

Hi everyone!

A new release is now available.

v0.1.4 includes several performance improvements, bug fixes, and feature refinements. Check out the release notes [here](https://github.com/flox/flox/blob/main/doc/release-notes/rl-0.1.4.md) for more details, and upgrade via your preferred package manager [here](https://floxdev.com/docs/).

Happy hacking!

---

<div class="post-metadata">

**Author:** ![alexdelprete](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/alexdelprete/32/554_2.png) [@alexdelprete](https://discourse.flox.dev/u/alexdelprete)\
**Post date:** [April 22, 2023, 2:06am UTC](https://discourse.flox.dev/t/release-announcement-v0-1-4-april-20-2023/734/2 "2023-04-22T02:06:51Z")

</div>

Hi,

I’ve upgraded to 0.1.4-r446-0.0.10-r224 and I noticed this error when I start the shell:

```bash
path '/root' does not contain a 'flake.nix', searching up
error: could not find a flake.nix file

```

I’m activating the default environment via `.zshrc` with `. <(flox activate)`.

With previous version I didn’t have this issue.

Any suggestion?

---

<div class="post-metadata">

**Author:** ![aameen](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/aameen/32/564_2.png) [@aameen](https://discourse.flox.dev/u/aameen)\
**Post date:** [April 25, 2023, 5:09pm UTC](https://discourse.flox.dev/t/release-announcement-v0-1-4-april-20-2023/734/3 "2023-04-25T17:09:30Z")

</div>

Howdy, thanks for the report.

I have a theory about why this is occurring, and I am going to file a ticket for our engineers.

I think in the short term you could use a more explicit invocation : `. <( flox activate -e default; );` which should tell `flox` that you are trying to activate the default environment “global” to the user, as opposed to a project.

I suspect this crash occurs when you open a shell inside of a `git` repository, so it’s trying to locate a “project environment” in that tree.

---

<div class="post-metadata">

**Author:** ![alexdelprete](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/alexdelprete/32/554_2.png) [@alexdelprete](https://discourse.flox.dev/u/alexdelprete)\
**Post date:** [April 25, 2023, 11:18pm UTC](https://discourse.flox.dev/t/release-announcement-v0-1-4-april-20-2023/734/4 "2023-04-25T23:18:10Z")

</div>

> [@aameen](#):
>
> I think in the short term you could use a more explicit invocation : `. <( flox activate -e default; );`

Hi Alex, thanks for getting back to me. This worked, thank you.

I thought I didn’t need to specify the default environment since I wasn’t specifying a project. In previous versions my assumption was correct.

> [@aameen](#):
>
> I suspect this crash occurs when you open a shell inside of a `git` repository, so it’s trying to locate a “project environment” in that tree.

It’s not strictly a git repo, it’s the dotfiles environment, managed by [chezmoi](https://www.chezmoi.io/), which uses git to manage it.

---

<div class="post-metadata">

**Author:** ![aameen](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/aameen/32/564_2.png) [@aameen](https://discourse.flox.dev/u/aameen)\
**Post date:** [April 27, 2023, 1:12pm UTC](https://discourse.flox.dev/t/release-announcement-v0-1-4-april-20-2023/734/5 "2023-04-27T13:12:53Z")

</div>

Gotcha. This sounds like a bug to me, I think what we ought to do is get flox to fall back to globally defined envs if a project doesn’t contain an environment.

I am confused about whyits attempting to search for project environments when you aren’t in a git repo but our engineers will look into it

---

<div class="post-metadata">

**Author:** ![alexdelprete](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/alexdelprete/32/554_2.png) [@alexdelprete](https://discourse.flox.dev/u/alexdelprete)\
**Post date:** [April 28, 2023, 1:55am UTC](https://discourse.flox.dev/t/release-announcement-v0-1-4-april-20-2023/734/6 "2023-04-28T01:55:52Z")

</div>

> [@aameen](#):
>
> I am confused about whyits attempting to search for project environments when you aren’t in a git repo but our engineers will look into it

Just speculating here, but maybe one of these files triggers the logic?

![image](https://canada1.discourse-cdn.com/flex036/uploads/floxdev/original/1X/6c8087644961368ad82076aed2b8de7f05fe8fe7.png)

---

<div class="post-metadata">

**Author:** ![aameen](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/aameen/32/564_2.png) [@aameen](https://discourse.flox.dev/u/aameen)\
**Post date:** [May 1, 2023, 2:08pm UTC](https://discourse.flox.dev/t/release-announcement-v0-1-4-april-20-2023/734/7 "2023-05-01T14:08:02Z")

</div>

Thanks for the follow up, I think you’re probably right. I’ll pass this along to help folks debug.

Did using `-e` help you?

---

<div class="post-metadata">

**Author:** ![alexdelprete](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/alexdelprete/32/554_2.png) [@alexdelprete](https://discourse.flox.dev/u/alexdelprete)\
**Post date:** [May 1, 2023, 10:42pm UTC](https://discourse.flox.dev/t/release-announcement-v0-1-4-april-20-2023/734/8 "2023-05-01T22:42:37Z")

</div>

> [@aameen](#):
>
> Did using `-e` help you?

Perfectly. I reported back in my first reply to your suggestion. Thanks again.