# Stability missing from flox search?

**URL:** <https://discourse.flox.dev/t/stability-missing-from-flox-search/763>\
**Category:** Developing with flox\
**Tags:** closed\
**Created:** [June 29, 2023, 12:14pm UTC](https://discourse.flox.dev/t/stability-missing-from-flox-search/763 "2023-06-29T12:14:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon59756714](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@anon59756714](https://discourse.flox.dev/u/anon59756714)\
**Post date:** [June 29, 2023, 12:14pm UTC](https://discourse.flox.dev/t/stability-missing-from-flox-search/763/1 "2023-06-29T12:14:17Z")

</div>

I was not understanding why `flox upgrade` did not bump a version of yq-go to newest that has some nice patches. I used `flox search -l yq-go` to see if new version is available and it was. But it seems by default packages are installed in stable stability. It’s not visible because it’s default and I had to issue `flox install unstable.nix-pkgs.yq-go` to get new version (along the old no-stability-defined one)

Was there a change to not show stabilities in search? It makes things confusing, maybe not now after I understood the default is stable and stability has to be changed manually if newer version is needed.

Is the new recommendation using the @ version instead of stabilities?

---

<div class="post-metadata">

**Author:** ![Samuel\_Rose](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/samuel_rose/32/515_2.png) [@Samuel\_Rose](https://discourse.flox.dev/u/Samuel_Rose)\
**Post date:** [August 10, 2023, 9:34pm UTC](https://discourse.flox.dev/t/stability-missing-from-flox-search/763/2 "2023-08-10T21:34:15Z")

</div>

We did indeed make some changes to simplify search results.

Part of the new recommendation indeed is to use the @ version. I am looking into having our documentation updated to reflect what we recommend when people are looking to install outside of the `stable` stability. i’ll follow up ASAP when I have more information than this, and thank you so much!
