WPWatchtower

WordPress plugin updates, delivered as pull requests with the proof attached.

WPWatchtower watches your WordPress site for vendor plugin updates, takes the safe ones through your develop environment, and opens a pull request into preprod with the evidence in the body. Anything that is not clearly safe becomes an issue with the research already done.

For teams running git-deployed WordPress with a pull-request workflow on enterprise hosting, where plugin updates happen in batches because each one costs a developer an afternoon.

How a cycle works

  1. Scan and classify

    Every site, every vendor plugin, every pending version. Each update is sorted by tier: patch-only, minor-and-patch, or issue-only.

  2. Update and test on develop

    One branch per plugin. Merged to develop, deployed, then checked: fatals, rendered pages, the plugin's own surface, your existing test suite.

  3. Pull request or issue

    A clean run becomes a pull request into preprod with the evidence in the body. Anything else becomes an issue with the research already done.

  4. Retro

    Each cycle updates a per-plugin blueprint, so the next run for that plugin starts from what the last one learned.

What it never does

  • merges to preprod or production. Those are your promotion steps.
  • hides one update behind another. One plugin per branch, per pull request.
  • reverts on its own. A failed check holds the state and alerts a person.
  • edits vendor plugin code. A compatibility problem is an issue with a proposed fix.
  • counts a check that could not run as passed. BLOCKED is not evidence.

Early access

We are onboarding a small number of design-partner sites. Leave your email and, if you like, a line about your site or hosting setup. Someone on the team replies.