Automated Crates.io Docs Build Failure Alerts
Every hour, WebRun opens crates.io, checks the documentation build status for each crate your team maintains, texts the maintainer through Twilio the moment a docs build breaks, and saves the failing build log to a Google Drive folder so broken documentation gets fixed instead of sitting live and unreadable.
How do I get alerted when a crate's documentation build fails?
WebRun checks the documentation build status for every crate your team maintains, every hour. It texts the maintainer through Twilio the crate and version the moment a docs build breaks, and saves the failing build log to Google Drive, so broken documentation gets fixed instead of sitting live and unreadable.
- Broken docs builds get a text within the hour they fail
- Build logs are saved automatically for faster debugging
- Published crates never sit long with unreadable documentation
Built for Rust maintainers · open source maintainers · platform teams · developer tooling teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
crates.io/loginin a real browser with your saved login - no setup, no API keys. -
1
Crates.io - check the docs build status
- Open the crates.io page for each maintained crate
- Check its documentation build status
- Capture the crate name and version for any build that failed
Done when Every maintained crate's documentation build status is checked, with failures listed.
-
2
Twilio - text the maintainer
twilio.com
WebRun opens Twilio to text the maintainer. - Text the maintainer the crate name and version for each newly failed docs build
- Link the crate's documentation page
- Send one message per crate, not a batch
Done when The maintainer has a text for every newly failed documentation build.
-
3
Google Drive - save the failing build log
drive.google.com
WebRun opens Google Drive to save the failing build log. - Save the failing build log for each broken documentation build
- Name the file with the crate name and version
- Skip crates already logged this hour
Done when Every newly failed documentation build has its log saved to Drive.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it publish a new crate version to fix it?
No. WebRun only reports the failed documentation build. Publishing a fix is always a deliberate action your maintainer takes.
Does this affect the crate itself?
No. It only checks the documentation build status. The published crate and its code are untouched.
How fast does a broken docs build get reported?
Within the hour it happens, since every maintained crate's docs status is checked each hour.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.