You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 25c5998
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/internals/providers.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ mise tool; mise must resolve the binary and list it in an active install of that
97
97
path must be a shim or under the tool's `latest` link, which the upgrade repoints: a version
98
98
directory (including one `mise activate` put on `PATH`) would keep running the old binary until mise
99
99
prunes it. Everything else mise touches (fixed version paths, pinned tools, wrappers, OpenCode 1.x,
100
-
whose mise tool crosses into 2.x) stays manual-only, so T3 Code never edits mise config. `mise latest` supplies the version, because settings such as
100
+
whose mise tool crosses into 2.x) stays manual-only, so T3 Code never edits mise config. Nix store installs stay manual-only too, since the store is read-only. `mise latest` supplies the version, because settings such as
101
101
`minimum_release_age` can hold mise behind npm. A Grok cask whose Homebrew prefix
102
102
cannot be verified also stays manual-only: `grok update` would install a second copy. npm updates pin `--prefix` because the
103
103
`npm` on `PATH` can belong to a different Node than the one that owns the provider. Homebrew
0 commit comments