Skip to content
This repository was archived by the owner on May 29, 2026. It is now read-only.
This repository was archived by the owner on May 29, 2026. It is now read-only.

[BUG] Changes to an included ENV do not automatically propogate #358

Description

@jaydeland

Background

When our base flox env is updated we would expect flox env that include it to automatically get the updates. Currently we have to remove the manifest.lock file or run flox include upgrade

Steps to reproduce

  1. step 1
  • Update a flox env that is included in another flox env via the include section in the manifest.toml
  1. step 2
  • Run flox activate in the flox env that includes the base
  1. step 3 What is the current behavior?
  • The project will activate without the changes from the base

What is the expected behavior?

  • The project will automatically update with the latest changes from the base. This is part of the benefit of having a layered system like this - make a change in the base and all projects that include it will get it.

[ ] -
[ ] -

Possible Fix

Supporting material

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdocumentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions