Automated Krita Release Version Watch
Every Monday, WebRun opens krita.org, compares the current release against the version your studio runs, reads the release notes for what changed, posts the version and the highlights to Slack, and briefs the wider studio in Microsoft Teams so artists update together.
How do I keep a design studio on the same software version?
Every Monday WebRun opens krita.org, checks the current release against the version your studio runs, and reads the release notes for what changed. It posts the version and the highlights to Slack and briefs the studio in Microsoft Teams, so everyone updates together instead of drifting across versions.
- The studio hears about a release the Monday after it lands
- Artists move versions together instead of drifting apart
- Quiet weeks produce no post, so the channel stays useful
Built for art directors · studio leads · illustration teams · game art 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
krita.orgin a real browser with your saved login - no setup, no API keys. -
1
Krita - check for a new release
krita.org
WebRun opens Krita to check for a new release. - Open krita.org and read the current release version on the download page
- Compare it against the version your studio has standardised on
- Read the release notes and pull out the fixes and changes that affect how your artists work
- Note whether the notes mention any plugin or file format your studio depends on
Done when The current release, its version, and the changes that matter to your studio are captured.
-
2
Slack - post the version and highlights
slack.com
WebRun opens Slack to post the version and highlights. - Post the new version to your art channel with the highlights from the release notes
- Say plainly whether this is a bug fix release or one that changes how a tool behaves
- Stay quiet in weeks when the version has not moved
Done when The art channel knows a release landed and what it changes.
-
3
Microsoft Teams - brief the wider studio
microsoft.com
WebRun opens Microsoft Teams to brief the wider studio. - Send the studio lead a short Teams brief with the version, the notable changes, and anything affecting plugins
- Recommend a date for the studio to move together rather than one artist at a time
- Leave downloading and installing to your people. WebRun never downloads or installs software
Done when The studio lead has what they need to call an update date.
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 download or install the update?
No. WebRun reads the release page and reports what changed. Downloading and installing stays with your people, and the policy blocks shell commands and uploads outright.
What happens in a week with no release?
Nothing is posted to Slack. WebRun only speaks up when the version has actually moved, so the art channel does not fill with weekly no change messages.
Does it explain what changed?
Yes. The post carries the highlights from the release notes and says whether it is a bug fix release or one that changes how a tool behaves, so artists know what to expect.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.