There was an internal error that triggered these incorrect webhooks. No mentioned packages were actually run. We apologize for any confusion this has caused.
Posted May 07, 2019 - 13:42 UTC
Investigating
We are investigating a potential issue with wrong webhook notifications being sent to some of our customers.