Ordinary plugin command failures no longer get reported as crashes.
What's wrong with this entry?
Install, uninstall, enable, disable, update and prune now raise a dedicated plugin-failure error when an operation reports failure. The shared handler only sends a report to error tracking when the error is neither that class nor otherwise classified, tagged per subcommand, so ordinary plugin failures stop being counted as unclassified crashes.
plugin operation returned a failure result
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.