PackageManager ID conflict on update

[mrhe (Mariusz Hermansdorfer)]

Seems that this thread is full of similar reports:

Yak issue switching versions

I have a plugin which I deploy through yak. The yak package contains 3 rhino plugins, and 1 grasshopper plugin. When users try to switch versions using yak. They have issues with the larger plugin which we’ll call Alpha. Say they switch from v1 → v2. It seems that Rhino seems to have already referenced Alpha v1 and is unable to release it to reference v2. I cannot figure out why this. Performing the install via the Yak CLI with Rhino closed works flawlessly. Any help is appreciated as nothin…