Enabling a plugin with disabled dependencies now stops and prints the enable commands to run first.
What's wrong with this entry?
If a plugin's dependencies are installed but switched off, enabling it now stops with a message naming them and giving the exact plugin enable commands to run first.
currently disabled. Enable
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
PR review artifacts can carry an "Approve on GitHub" button
Both mention enable
-
v2.1.248
Telemetry enablement read through a helper
Both mention enable
-
v2.1.221
Inline /mcp enable/disable detects changes made in another session
Both mention enable