I’m not sure, I don’t compile any of the grasshopper or rhinocommon dlls, and my projects simply refer to SR0 versions. As Rhino and Grasshopper load the dlls prior to my plugin, if there was a version conflict there would be a different runtime error (but McNeel don’t tend to break compatibility).
I don’t know how often scripts reference loaded rhino/grasshopper plugins, but I would have thought it would be common the plugin is built against an earlier version. I don’t recall seeing this warning flagged in older versions of Grasshopper, but I haven’t rolled back to check this.
This isn’t a big deal, but as I mention, it’s not ideal to see an orange component with warnings when it isn’t causing problems. If anyone has other suggestions, that’s great.