It doesn't require the implementation of an update hook, but if it is implemented it should be configured correctly. I've had a bunch of plugins that just copy pasted the hook from other plugins, with the fun side effect that they'd trigger an update notification if the other plugin was updated, which prompted the addition of this note to the registration check list.
But if you don't want to implement the update hook (or not yet), you can, it's not mandatory.
It doesn't require the implementation of an update hook, but *if* it is implemented it should be configured correctly. I've had a bunch of plugins that just copy pasted the hook from other plugins, with the fun side effect that they'd trigger an update notification if the *other* plugin was updated, which prompted the addition of this note to the registration check list.
But if you don't want to implement the update hook (or not yet), you can, it's not mandatory.
As discussed at MRMCD. Pretty please with a cherry on top? 😊
it's #NotABug
For reference: https://plugins.octoprint.org/help/registering/
Also depends on me adding some kind of update mechanism, so probably ... soon™
It doesn't require the implementation of an update hook, but if it is implemented it should be configured correctly. I've had a bunch of plugins that just copy pasted the hook from other plugins, with the fun side effect that they'd trigger an update notification if the other plugin was updated, which prompted the addition of this note to the registration check list.
But if you don't want to implement the update hook (or not yet), you can, it's not mandatory.
Oh, that's nice. Then there will be a pull request soon.
https://github.com/OctoPrint/plugins.octoprint.org/pull/636