Craft CMS updates, sent as pull requests.
VerWatch keeps track of Craft and every plugin across the sites you look after, and on the schedule you choose it opens a pull request for staging and production. Each plugin stays on its major version and is checked against the Craft release you run, so what turns up is an update you can review and merge.
Free while in beta Craft 3, 4 and 5 PHP 7.4 to 8.5
From a connected repo to a Craft update you can merge.
VerWatch does the routine part of Craft maintenance (checking versions, running the update, opening the PR) and your team keeps the review.
-
01
Connect GitHub.
Install the VerWatch GitHub App on your Craft repos. Each project's composer.lock syncs straight away, and again whenever a push changes it.
-
02
See every site at once.
Craft and each plugin are compared against Packagist and the Craft version the site runs, with security advisories and releases that plugin developers mark as critical pushed to the top.
-
03
Review the pull request.
On your schedule the update runs in an isolated container, Craft applies its own migrations and project config, and a pull request lands on your branch for your CI and your team to check.
Everything around a Craft update, handled.
Running composer update is the easy part. VerWatch also covers which sites need what, who hears about it, and what happens when one plugin needs patching on forty sites at once.
Automated update PRs for staging and production.
One run works out a single set of versions and opens a pull request on each branch, so what you test on staging is exactly what ships to production. Every plugin it moves is listed with its old and new version, and if the two branches can't take the same change the run stops and tells you why.
- Craft runs its own migrations with craft up, so project config changes arrive in the same PR
- A comment on the PR traces each project config change back to its migration and changelog entry
- Auto-merge staging, everything, or nothing, per project
Every plugin, sorted by what needs doing.
Each project lists Craft and its plugins as urgent, outdated or up to date, with the installed version beside the newest one the site can safely take and a link to the changelog. The site's Craft and PHP versions sit at the top of the page.
- Critical releases and Packagist advisories marked by severity
- Compatible versions respect your Craft version and major version
- Plugins with an expired licence are badged, and you choose whether runs update them
One plugin, every site that runs it.
Open any plugin to see which of your sites have it installed and which version each one is on. When a plugin ships a critical fix you can see every affected site on one page, pick the ones to update, and start a run on each of them from there, limited to that plugin and the dependencies it needs.
- Filter by GitHub org, Craft version or status
- Sites that can't take the update yet are marked as blocked
- Patch a vulnerable plugin across a portfolio from one page
Update schedules that suit each client.
Put sites on a shared monthly or quarterly schedule, or give a project a cadence of its own. Runs happen in your timezone, can be nudged off a weekend to the following Monday, and keep a full history of every attempt and outcome.
- Shared schedules move a group of sites together
- A calendar feed shows what's due in your own calendar app
- Run any project or plugin by hand whenever you need to
Updates that follow the rules of the Craft updater.
VerWatch picks versions the way you would if you were updating a Craft site by hand, so a run doesn't propose something you'd have to back out of.
- Craft 3, 4 and 5
- tracked side by side on one dashboard
- PHP 7.4 to 8.5
- every PHP version the updater ships
- 2 branches
- staging and production in a single run
Stays on the major version.
A plugin on 4.x can move to any later 4.x release but never to 5.0, and that includes craftcms/cms, so a scheduled run never turns into a Craft upgrade.
Checked against your Craft version.
Every plugin release is checked against the Craft version the site runs, so a Formie release that needs Craft 5 stays put on a Craft 4 site instead of breaking the resolve.
Resolved for your PHP version.
Composer resolves against the PHP version the project runs, from 7.4 to 8.5, so an update won't pull in a release your server can't load.
Flags expired licences.
Plugins whose Craft licence has lapsed are marked with an Expired License badge, and update runs include them unless you switch that off for the team or for a single project.
More features
Critical notifications.
When an advisory lands that rates critical (or high, if you set the bar there), the whole team hears about it within minutes on the dashboard and by email, with a count of the sites it affects.
Slack updates.
Connect a channel and each run posts there as it happens: when its pull requests are ready, when it fails, and when the update is merged into production, with a link back to VerWatch.
One digest email.
Notifications about update runs are rolled into one email per person, sent once your team's runs have been quiet for 15 minutes (or 2 hours after the first, if they never are), so nobody gets forty separate notifications about forty sites.
Team workspaces.
Invite the people who look after the sites as owners, members or read-only viewers, and connect as many GitHub orgs as your clients use.
MCP server and API.
Ask Claude or Cursor which sites still have a vulnerable plugin, or let CI start an update. Projects, packages, advisories and update history are readable over a REST API and an MCP server.
End of life and PHP ceilings.
Craft and PHP releases are checked against their end-of-life dates, and when a plugin can't move because of the project's PHP version the badge says so, rather than leaving you to work it out from a failed run.
Running on agency portfolios already.
Studios that look after Craft sites for clients put their updates through VerWatch.
Keeping 40+ Craft sites on a dev's machine just to run the monthly updates was an unnecessary use of resources and a point of failure. VerWatch solves that for us, freeing up devs and letting more of the team manage the update process.
Updates for our client sites used to be a job somebody had to remember. Now they get staged automatically and we just sign them off to go live. Every month it's saving us hours and maybe days of time.
Free while in beta.
Sign in, connect your repos and start running updates. There's nothing to pay while VerWatch is in beta, and you'll hear from us well before that changes.
Questions about Craft updates, answered.
Can't find what you're after? Ask us and a person will reply.
How do I keep Craft CMS plugins up to date across lots of sites?
Connect their GitHub repos and VerWatch tracks Craft and every plugin on all of them from one dashboard. Each project gets an update schedule, and every run ends in a pull request with the new versions.
Will an update break my Craft site?
Nothing reaches production without a pull request you review. Every plugin stays inside its current major version and each release is checked against the Craft version the site runs. By default a run merges the staging pull request so you can test there, and leaves production for you.
Does VerWatch run craft update?
Yes, in effect. It updates through Composer the way the Craft updater does, then runs craft up so Craft writes its own project config changes, and all of it lands in the same pull request.
Does it work with Servd, Craft Cloud or Forge?
Yes. VerWatch only ever opens pull requests on GitHub, so whichever host deploys from your repo picks up the update when you merge.
Which versions of Craft and PHP are supported?
Craft 3, 4 and 5, with the updater running PHP 7.4 through 8.5. Each run resolves against the PHP version your project uses, so it never proposes a release your server can't load.
What access does VerWatch need?
You install the VerWatch GitHub App on the repositories you choose. It reads composer.json and composer.lock to track dependencies, and opens pull requests for updates.
How do I get started?
Sign in with GitHub or an emailed link, name your team, and install the GitHub App on the repos you want tracked. Your account is created on first sign-in, and it's free while VerWatch is in beta.