Hi mcneel,
We have issues that when we install through yak (inside rhino) then it adds the newest version of our plugin but it does not remove the old ones. Next time we open rhino it loads the old one instead of the newest.
Are you installing a public yak package @sonderskovmathias?
No it’s an internal.
If no one else is experiencing this, then maybe we screwed the manifest ?
ons. 25. mar. 2026 kl. 18.38 skrev Callum Sykes <notifications@mcneel.discoursemail.com>:
Would you be able to send me two versions of it? Ideally the two versions you’re having conflicts with.
As Callum well knows, relates to Package Manager Update grasshopper conflict - Rhino Developer - McNeel Forum and other threads.
It’s not clear to me why package manager needs to retain old package versions. If it’s necessary for some plugins, it would be good if packages could opt out of having old versions retained using the manifest. From the outside, it seems that downloading is easy and practical for upgrading, why is it not the case for downgrading? I’m assuming McNeel keep statistics on this, is it common for users to downgrade plugins?
I do I do, I want to collect as many of these issues as repeatably as possible and create tickets so the appropriate dev can fix them as I think yak should be an entirely seamless experience.
We don’t keep many statistics at all, and this is not something we track as far as I know. I would imagine not many, and even then you can just download it from yak again rather than using the one on your drive.
I hope I’m not reviving an old post for an already solved issue. I noticed that having the package manager set to automatically update on login means you need to restart Rhino twice to get the plugin fully updated. On first restart, the plugin manager shows it has loaded the old version and the package manager shows it has loaded the new version (I’m guessing the plugin is loaded before the package manager makes its updates?) So then you need to restart Rhino a second time so that the plugin manager reads the new version from the package manager and updates completely to the new version.
Perhaps this is functioning as intended? Or I am doing something wrong. But it seem counterintuitive to have to restart twice to get a plugin/package update fully complete