pin-latest: local doesn't seem to work

[ApproachingApathy]

What version?

0.50.1

Which command?

proto pin

What happened?

I have pin-latest set to local at $XDG_DATA_HOME/proto/.prototools.

[settings]
auto-install = true
pin-latest = "local"

However, running proto pin pnpm latest results in the following.

pnpm = "latest"

My understanding is that pin-latest = "local" should resolve the version and save it in the current directory's .protofile. I would expect to see this:

pnpm = "10.12.1"

or even

pnpm = "^10.12.1"

Trace logs?

No response

Operating system?

Linux

Architecture?

x64

[milesj]

@ApproachingApathy pin-latest only triggers during proto install, not proto pin.

[ApproachingApathy]

I just tried and it doesn't seem to work.

personal-site-v3 via ⬢ v24.2.0 on 🐳 v5.5.1 (podman.sock)
➜ cat $XDG_DATA_HOME/proto/.prototools
bun = "1.2.5"
go = "1.24.3"
pnpm = "9.8.0"
uv = "0.7.3"
yarn = "1.22.22"
node = "24.2.0"

[settings]
auto-install = true
pin-latest = "local"

personal-site-v3 on  main [!+] via ⬢ v24.2.0 on 🐳 v5.5.1 (podman.sock)
➜ proto install

node
pnpm

│ SUCCESS
│ Installed node and pnpm in 0s!


personal-site-v3 on  main [!+] via ⬢ v24.2.0 on 🐳 v5.5.1 (podman.sock)
➜ cat .prototools
pnpm = "latest"
node = "latest"

I don't think it's reading my global config? If I set pin-latest in the local file it works. I have a global config at $XDG_DATA_HOME/proto/.prototools

personal-site-v3 on  main [!+] via ⬢ v24.2.0 on 🐳 v5.5.1 (podman.sock)
➜ cat $XDG_DATA_HOME/proto/.prototools
bun = "1.2.5"
go = "1.24.3"
pnpm = "9.8.0"
uv = "0.7.3"
yarn = "1.22.22"
node = "24.2.0"

[settings]
auto-install = true
pin-latest = "local"

personal-site-v3 on  main [!+] via ⬢ v24.2.0 on 🐳 v5.5.1 (podman.sock)
➜ proto install


node
pnpm

│ SUCCESS
│ Installed node and pnpm in 0s!


personal-site-v3 on  main [!+] via ⬢ v24.2.0 on 🐳 v5.5.1 (podman.sock)
➜ cat .prototools
pnpm = "10.12.2"
node = "24.2.0"

[settings]
pin-latest = "local"

I see here, https://moonrepo.dev/docs/proto/config#upwards, that maybe install doesn't use the global config by default. Is there a way to configure install to use upwards-global as it's default? I'm aware that it might work if I defined a ~/.prototools but I not sure it makes sense that "global" settings are ignored on install.

[milesj]

Correct, proto install does not read global by default. The reasoning is, is when you got to a project/repo that has .prototools, and you run install, you only want to install what's in that file, not the X other things that exist globally.

There's no way to configure this. You would just need to pass --config-mode.

[ApproachingApathy]

Thanks. I do feel that it makes more sense for settings defined in a global config to apply globally during install, but I understand that there might be reasons for why it might not be desired to read the global config for dependencies. I think I'll just move my global config to the user ~/.prototools.

[milesj]

Yeah I would say, almost never use global config. That's more for proto to store some stuff itself. User config is probably better.