Is winget a supported install path for v2, and how does sync's `upgrade` interact with it?

winget is still on 1.2.2 - v2 hasn't been submitted yet. The manifests have always come from the community rather than from you, so v2 will land there whenever someone gets round to it.

Two questions off the back of that:

1. Is winget a supported way to install v2, or would you rather people used the installer directly?

2. The source docs say sync.exe handles upgrade. If nvm can upgrade itself, a winget-managed install ends up on a different version than the one winget recorded, and winget upgrade stops lining up. Should self-upgrade be off when nvm came from a package manager?

I use winget for most things, so I'm happy to submit the v2 manifest - unless you're planning to do it yourself. Either way there's one call that's yours: the package is currently CoreyButler.NVMforWindows, and the repo has since moved to the nvm-windows org, so I don't know whether you'd want the identifier to stay as it is.