Best practice to prevent auto-update of packages?

Grasshopper Developer
, , ,
1

Hi Guys,

I’ve run into a second dependency auto-update issue in less than a month today.

Both have been the author has updated/released there MacOS R8 version:

  • LunchBox
  • OpenNest

In BOTH cases the latest version is not available in R7 and I need to keep my single code base in R7 for at least another year. So my working code breaks in R8 if the dependencies auto update.

In both of the above cases I happen to be using 1 or 2 useful functions, nothing related to the main use of the plugin. Also my clients have zero interest in GH or GH plugins, they just want my code to work.

With a stable install of plugins is there a way to disable auto updates so my clients don’t see these issues?

Cheers

DK

2

The clients will have to disable auto-updating of plug-ins:

image
image346×603 17.1 KB

-wim

3

Thanks for surfacing the global option in a more convenient place than the advanced options! Would it be possible to allow freezing updates on a per-package basis? For one example of how this would be useful - I have a workflow that depends on one specific version of a plugin, while all others should be allowed to update freely, etc.