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
- step 1
- Update a flox env that is included in another flox env via the include section in the manifest.toml
- step 2
- Run flox activate in the flox env that includes the base
- 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
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 upgradeSteps to reproduce
What is the expected behavior?
[ ] -
[ ] -
Possible Fix
Supporting material