Automated Blender Extension Compatibility Watch
Every Monday, WebRun opens the Blender extensions your pipeline depends on, reads each one's latest version and which Blender versions it supports, texts you through Twilio when something your team runs is about to break, and leaves a drafted rollout note in Gmail for the artists to read.
How do I track Blender extension updates and version compatibility?
WebRun checks the Blender extensions your pipeline depends on every Monday, reading each one's latest version and the Blender versions it supports. It texts you through Twilio when something your team runs will break and drafts a Gmail rollout note for artists, so upgrades are planned rather than discovered mid project.
- Breaking extension changes are known before an artist hits them
- Every update arrives with the author's own release notes
- The rollout note is written for you and sent by you
Built for pipeline leads · 3D studios · technical artists · VFX and animation 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
www.blender.orgin a real browser with your saved login - no setup, no API keys. -
1
Blender - check extension versions and support
blender.org
WebRun opens Blender to check extension versions and support. - Open each extension on your dependency list and read its current version and release date
- Read which Blender versions it lists as supported and compare that with the version your team runs
- Capture the release notes for anything that changed since last week, keeping the wording the author used
- Mark each extension as current, updated this week, or unsupported on your Blender version
Done when Every extension on the list has its version, support range, and change since last week recorded.
-
2
Twilio - text you about a breaking change
twilio.com
WebRun opens Twilio to text you about a breaking change. - Text you only when an extension no longer supports the Blender version your team runs, or a major version landed
- Name the extension, the new version, and what the release notes say changed
- Send to your own pipeline team numbers only, and stay quiet on a week with no breaking change
Done when You have been texted about any extension that will break on your current Blender version.
-
3
Gmail - draft the rollout note for artists
gmail.com
WebRun opens Gmail to draft the rollout note for artists. - Draft a short weekly note to the artist list with what updated and what to install
- Say plainly which extensions to leave alone until the pipeline is tested
- Leave it in Drafts. WebRun never emails the team without the pipeline lead sending it
Done when A drafted rollout note sits in Gmail waiting for the pipeline lead to review and send.
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 install or update anything on my machines?
No. WebRun reads version and support information and reports it. Installing an extension or upgrading Blender stays with your pipeline lead, and no file is downloaded by a run.
Will it email the artists without me?
No. The rollout note is left in Gmail Drafts for the pipeline lead to review and send, so nothing reaches the team until a person approves the wording.
How does it know an extension will break?
It compares the Blender versions each extension lists as supported against the version your team runs, and flags anything that has dropped support or shipped a major release.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.