Enforcing stricter version compatibility checks in plugin CLI install commands
Enforcing stricter version compatibility checks in plugin CLI install commands
Since Grafana v10.2, the endpoint to check compatible versions when installing a plugin using grafana cli plugins install changed, which led to Grafana dependency versions no longer being taken into account. This might have led to the CLI installing plugins that are not fully compatible based on the plugins definition of compatibility via the grafanaDependency property in the plugin.json file.
The Grafana version check is re-enabled in Grafana v12 when installing plugins.
Grafana Cloud users are not affected as they can’t use the CLI to install plugins. We expect there are only a handful of cases for self-managed instances.
What to do if I want to ignore the compatibility check?
We do not recommend installing plugins declared as incompatible. But, if you really have to force install a plugin despite it being declared as incompatible, refer to the Installing a plugin from a ZIP guidance.
