Repository navigation
Resolving vars in tools version fails in tracked config when not in current directory #15482
Replies: 1 comment
|
This happens because The experimental identity install layout avoids this. It records what each project's templated versions rendered to when you use the project, and prune reads that record instead of re-rendering. If a project has no record yet, prune keeps every install of the templated tool until you use the project again. Enable it with: [settings]
experimental = true
install_layout = "identity"See Identity install layout. Existing installs stay where they are and keep working. AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: 2.1.317. |
Uh oh!
There was an error while loading. Please reload this page.
I have a project where I have defined a variable used in both a tool version and some environment variables.
When mise operates in the project directory, everything works as it should.
However, when mise does a check of tracked configs from a different directory (for instance looking for things to clean up), the resolution of variables fails:
Contents of
~/code/gjensidige/gappynator/.config/mise/config.toml:mise-doctor.txt
All reactions