Some days ago we discovered that CircleCI stopped sending these webhhoks to the cc-slack-proxy server. We contacted CircleCi's support team and they shared that we should be using CircleCi's v2 of their webhooks, which are set either via the web UI or API. This webhooks v2 came with a different payload, and in order to avoid us changes on the cc-slack-proxy and on shipbot to support this new payload we opted for temporary using a custom webhook that simulates the old webhooks.
Some days ago we discovered that CircleCI stopped sending these webhhoks to the
cc-slack-proxyserver. We contacted CircleCi's support team and they shared that we should be using CircleCi's v2 of their webhooks, which are set either via the web UI or API. This webhooks v2 came with a different payload, and in order to avoid us changes on thecc-slack-proxyand onshipbotto support this new payload we opted for temporary using a custom webhook that simulates the old webhooks.