VerWatch timeline

1. Discovery Try out a preview for you Update runs Discovery

   Once a preview site is up, VerWatch would work through it the way you would: open every page in the navigation, follow each link to find any that are broken, fill in and send the forms, and try what the installed plugins do. What it tried and what it found would be listed on the preview panel and on the pull request, so you know how the update behaves before you merge it.

2. Discovery Pricing and plans Teams and accounts Discovery

   VerWatch is free while it's in beta. Before that ends we want to work out what the service is worth to the people using it, and what tiers suit a freelancer with a few sites as well as an agency with a whole portfolio, so that whichever plan you land on feels fair. We'll announce pricing well before anyone is asked to choose, and the beta stays free until then.

3. Discovery Run critical updates automatically Update runs Discovery

   An opt-in setting that starts an update run by itself when a critical release lands for a package a project has installed, so a fix published overnight is already a pull request when you start work. It would cover critical releases only, and how far the run merges would stay with the strategy you've already chosen.

4. Discovery Webhooks when an update completes Integrations Discovery

   Have VerWatch call a URL of yours when an update is completed on production, so your own tools can pick it up without polling the API. We're also looking at a second event for when a critical update becomes available.

5. Discovery Add manual projects Projects Discovery

   Add a project that isn't hosted on GitHub and still see which versions it's running. We're exploring two ways to collect the version numbers: a plugin installed on the site, or VerWatch logging in securely and reading them from the control panel.

6. Planned Expired licences across your team Packages and licences Planned

   See which plugin licences have expired across every project in a team, and which projects each one affects, without having to open the right project to find out.

7. Planned Other Git providers Integrations Planned

   Connect repositories hosted on GitLab, Bitbucket or Buddy and get the same package tracking and update runs as a project on GitHub, with pull requests opened on whichever provider hosts the code.

8. Testing Preview an update before you merge it Update runs Testing

   Open a preview site of the update in a sandbox, with your own content in it, and click through the pages and the control panel before choosing to merge. Upload a copy of the project's database and each preview runs on the updated code, goes to sleep when nobody has opened it for a while, and wakes again on the next visit. Any email the preview sends lands in its own mailbox rather than going out.

   • Each preview gets its own address on verwatch.com
   • A screenshot of the home page on the Preview tab once the site is up
9. Testing Warm updates Update runs Testing

   An existing pool of secure VMs is kept warm, ready to start updates while your team is active or a schedule is about to fire, so a run gets going straight away instead of waiting for its environment to boot.

10. Live

    Everything you can use in VerWatch today, with the newest at the top.

11. Oct 2026 Search projects and packages with Command+K Interface Oct 2026

    The header now has a search bar on every page, and pressing Command+K (or /) opens it from the keyboard. Type a name to jump to a project, or to a package's page, where every project using it is listed with the version each one is on. On a project's page the same bar offers Prepare updates and Sync project along with the project's tabs and its GitHub repository. It replaces the search field that sat above the dashboard's project table.

12. Oct 2026 A help page in the header menu Feedback and support Oct 2026

    The header menu has a Help link that opens a page explaining what VerWatch does and how each part of it works, in short sections grouped by area: projects, versions, security, update runs, scheduling, notifications and teams. It's there for when you want to check what a badge means or what a scheduled run will do, without leaving the app.

13. Oct 2026 Hear an update as it runs Interface Oct 2026

    An update run now plays a sound as it starts, at each stage it reaches and as its pull requests merge, so you can tell how it's going without watching the progress row. A run that fails or is cancelled sounds different from one that completes. If you'd rather work in silence, the Sounds toggle in your profile settings turns them all off for your account.

14. Oct 2026 What's new in the header menu Interface Oct 2026

    The header menu has a What's new link that opens this timeline at the work that's live. A blue dot sits on your picture and beside the link when something has shipped since you last looked, and the same dot marks each entry on the timeline that you haven't seen yet.

    • A count of unseen work beside the Live heading
15. Oct 2026 Gravatar pictures for accounts without GitHub Teams and accounts Oct 2026

    If you sign in with an email link and haven't connected GitHub, your picture in the header menu and in your team's member list is now the Gravatar for your email address. An address without a Gravatar keeps the initials it had before.

16. Oct 2026 Follow an update from any tab Update runs Oct 2026

    A running update now sits above the project tabs and stays there whichever tab you're on, saying what it's updating and how far it will merge. Its progress is a single row that opens to show every stage with its timing, and once the run finishes the pull requests take its place with their merge steps.

    • In queue status with your plan's concurrency limit
    • Prepare updates bar on package pages
    • Prepared, Staged and Completed used throughout
    • Strategies renamed Open PRs, Merge staging and Merge both
17. Oct 2026 A 4.0.4 to find on the 404 page Interface Oct 2026

    The 404 page hides a single 4.0.4 in a dark grid of lookalike version numbers that only light up under your cursor, and it keeps count of how many you've found and your fastest time.

18. Oct 2026 A notification drawer and a batched digest email Notifications Oct 2026

    The bell opens a drawer of your recent notifications grouped by day, and each one takes you to the run it's about with its row already open on the History tab. The update digest email now waits until a batch of runs has gone quiet and its notifications have sat unread for 15 minutes, so the batch arrives as one email.

    • Toasts link to the run too
    • Restyled emails with a manage notifications link
19. Oct 2026 Settings and schedules, reorganised Interface Oct 2026

    The schedule page is split into Shared, Custom and Calendar feed tabs, team and user settings follow the same layout, and API access is divided into separate pages for MCP, API tokens and the API reference. VerWatch is also light only for now, so the appearance setting has gone.

    • Integrations renamed Slack
    • New login page
20. Sep 2026 Project links that match GitHub Teams and accounts Sep 2026

    Project pages now sit at the same owner and repository path as they do on GitHub, so two organisations in one team can each have a repository with the same name, and renaming a repository on GitHub leaves its VerWatch link alone. Teams spread across several organisations see the organisation named beside each project and can search by it.

    • Owner/repo in page titles and toasts
    • API and MCP take owner/repo paths
21. Sep 2026 Project config changes you can check Update runs Sep 2026

    Update runs now install each site from its own project config and let Craft apply its migrations, so the config changes in a pull request are the ones Craft wrote itself. Each pull request gets a comment showing which migration made every change and the changelog entry behind it, and when a package can't reach its newest release, VerWatch names the package holding it back.

    • Held back badge with the reason
    • A note when a Craft update moves a plugin further than listed
22. Sep 2026 Sign in to VerWatch from Claude Integrations Sep 2026

    Claude can now connect to VerWatch by signing in with your account, so there's no access token to create and paste in first. Once connected it can find a project by name, repository or domain, link you to the project or run it's describing, and tell you who started each update or which schedule ran it.

    • Connected apps in settings, with a disconnect button
23. Sep 2026 Schedules that fit your calendar Scheduling Sep 2026

    Scheduled update runs can now go straight into your calendar, one at a time or as a feed that keeps itself up to date, and monthly schedules can land on a day like the second Tuesday. Shared schedules let a whole team work to the same cadence without setting up every project on its own.

    • Redesigned schedule page
24. Sep 2026 Security fixes that need you, first Security Sep 2026

    Every package now gets a single security rating on Craft's own severity scale, and only critical fixes count as urgent by default, so the dashboard shows straight away which projects need attention today and which can wait for their next scheduled run.

    • Urgent update banner on the dashboard
    • Dashboard tiles split by severity
    • Severity badges on each release in What Changed
    • Filter packages by GitHub organisation
25. Sep 2026 Update one package across many projects Update runs Sep 2026

    When a single plugin needs patching everywhere, you can pick it once and run the update across every project that uses it, instead of opening each project in turn.

    • Choose which projects to include
    • Archived projects left out automatically
    • Replaces an older open pull request for the same package
26. Sep 2026 Safer, more predictable update runs Update runs Sep 2026

    The updater now does more of the careful checking a developer would do by hand: it respects the PHP version each project actually runs on, holds back a package that would cause a regression and tries again without it, and gives staging and production the same set of changes so nothing reaches one without the other. When a run can't go ahead, it tells you why in plain terms.

    • Per-project PHP version setting, including PHP 8.5
    • No pull requests for changes that do nothing
    • Craft sites found outside the repository root
    • Easy-to-say names for every run, like autumn-firefly
27. Sep 2026 VerWatch in your own tools Integrations Sep 2026

    Teams on the Agency plan can read their projects, packages and update history through an API, or connect an AI assistant such as Claude over MCP to ask questions and start update runs. Everyone creates their own access token from their settings.

28. Sep 2026 One team across several GitHub organisations Teams and accounts Sep 2026

    Agencies that keep client work in more than one GitHub organisation can run everything from a single VerWatch team.

    • Guided welcome tour for new teams
    • Team switcher on settings pages
29. Jul 2026 A read-only viewer role Teams and accounts Jul 2026

    Invite someone as a viewer, a project manager say, and they can see the dashboard, package versions, update history and pull request status for every project in the team, but can't start an update, merge a pull request, or change a project or its schedule. Owners pick the role when they send the invitation and can change it later from the members page.

30. Jul 2026 See what changed before you update Packages and licences Jul 2026

    For each outdated package, VerWatch shows the changelog between the version you have and the one you'd move to, with warnings pulled out as callouts, so you know what you're approving before a run starts.

    • Changelogs matched to the right major version
31. Jul 2026 Annual billing and everyday polish Interface Jul 2026

    Plans can be paid yearly at a discount, and notifications arrive the moment something happens with a link straight to the update they're about.

    • More concurrent updates on higher plans
    • Bug reporter now takes questions and ideas too
32. Jul 2026 Plugin licence and end-of-life tracking Packages and licences Jul 2026

    VerWatch keeps an eye on plugin licences as well as versions, so you can see when a licence runs out, what the renewal will cost on the Plugin Store, and which packages have reached end of life.

    • Expired licence detection
33. Jul 2026 Slack notifications for update activity Integrations Jul 2026

    Connect a Slack workspace to your team and follow update activity (pull requests ready for review, production deploys and failed runs) in the channels you already watch.

    • One-click Slack workspace pairing
    • Team default channel with per-project overrides
    • Every project's channel managed in one place
    • Post any past run to Slack from its history
34. Jun 2026 In-app feedback and support loop Feedback and support Jun 2026

    Customers can report issues from inside VerWatch with page context attached, helping us move from problem reports to fixes faster.

    • Bug reporter widget
35. Jun 2026 Cleaner account and team onboarding Teams and accounts Jun 2026

    GitHub sign-in, email magic links, default team routing, and private beta invites now work together so teams land in the right place faster.

36. Jun 2026 Branded notifications and email Notifications Jun 2026

    Account, billing, and alert messages now share a consistent, branded look, with an in-app notification center keeping important updates in one place.

37. May 2026 Critical security digests Security May 2026

    When new critical advisories land, affected teams receive a batched email digest instead of noisy one-off alerts for every package.

    • Per-user digest rollups
    • Readable advisory summaries
    • Direct links back to affected projects
38. Apr 2026 Self-serve billing and team plans Billing Apr 2026

    Teams can pick a plan and manage their subscription directly, with billing handled securely through Stripe.

    • Team-level billing controls
39. Mar 2026 Recurring update schedules Scheduling Mar 2026

    Set per-project cadences in your local timezone so dependency work happens on a predictable rhythm instead of only when someone remembers.

    • Project schedule tab
    • Dashboard visibility into upcoming runs
40. Feb 2026 Automated Craft dependency updates Update runs Feb 2026

    Run Composer and Craft updates from VerWatch with isolated updater jobs, staged pull requests, and optional merge-to-production flows.

    • One-click update runs
    • Progress tracking through merge milestones
41. Jan 2026 Dependency visibility for Craft teams Packages and licences Jan 2026

    VerWatch syncs GitHub repositories, parses Composer lock files, tracks Craft CMS packages, and surfaces outdated or vulnerable dependencies.

    • Packagist version checks

Nothing on the list matches that yet.