Automated Blender Release Monitoring
Every Monday, WebRun opens blender.org, checks the current stable and long term support versions against the version your studio runs, reads the release notes for anything touching rendering, importers or add-ons, books a test window on your calendar when a new release has landed, and sends the studio a Telegram summary.
How do I keep track of new Blender releases and plan the upgrade?
WebRun opens blender.org every Monday and compares the current stable and long term support releases against the version your studio runs. When a newer release exists it reads the release notes, books a test window on your own calendar, and sends the studio a Telegram summary of what changed.
- A new release is noticed within a week, not months later
- Breaking changes are read before anyone upgrades a workstation
- The test window is already on the calendar when the release lands
Built for 3D artists · animation studios · VFX teams · pipeline technical directors
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 for a newer release
blender.org
WebRun opens Blender to check for a newer release. - Open blender.org and read the current stable release and the current long term support release
- Compare both against the version your studio has recorded as in use
- When a newer release exists, open its release notes and pull the changes touching rendering, file compatibility, and add-ons
- Note anything described as a breaking change or a removed feature
Done when You know whether a newer release exists and what changed in it.
-
2
Google Calendar - book the upgrade test window
calendar.google.com
WebRun opens Google Calendar to book the upgrade test window. - Open your Google Calendar
- Book a two hour upgrade test window in the next free slot when a new release has landed
- Put the version number and the key changes in the event description
- Create the event on your own calendar with no guests. Never send an invitation to the studio
Done when A test window sits on the calendar for the new release, or no release means no event.
-
3
Telegram - send the studio the summary
telegram.org
WebRun opens Telegram to send the studio the summary. - Send the studio chat the version number, the release date, and the changes that matter to your pipeline
- Call out breaking changes and removed features first
- Say when the test window is booked for
- Send nothing when there is no new release this week
Done when The studio knows what changed and when it will be tested.
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
Does it download or install Blender?
No. WebRun reads the release page and the release notes only. Downloads and installs are blocked by policy, so upgrading stays a deliberate step an artist or admin takes.
Will it invite the whole studio to the test window?
No. The event is created on your own calendar with no guests, so nobody receives an invitation. The studio hears about it through the Telegram summary instead.
What if no new version came out?
Nothing happens. No event is booked and no message is sent, so a quiet week stays quiet and the alert keeps its meaning when a release does land.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.