A site that stops reporting is as much a problem as a site that is down. This release tells you when a connector goes silent, and why.
What changed
When a site has not reported for a while, WebCrew now says so, with the reason the last sync failed: the plugin was deactivated, the site moved, the key was rotated, the host blocked the request. Failing syncs back off instead of hammering the site, and the operator gets one clear notification instead of a stream.
Also in this release
Security fixes found in the pre-launch audit, and dependency updates that CI now blocks on when a high or critical finding appears.
Everything in this release
| # | What shipped |
|---|---|
| 1 | Alerts when a connector stops reporting, with the reason a sync failed |
| 2 | Security fixes for the launch |
Releases follow the product's own numbering; between numbered versions we ship dated releases. What comes next, with its week, is on the roadmap.