Samuel Arendt

WordPress 7.2 stops auto-updating sites that run from a Git worktree or submodule

WordPress 7.2, scheduled for December 8, 2026, changes how core decides whether a site is under version control. The developer note published on November 19 on Make WordPress Core says that sites running from a Git worktree or submodule will no longer receive automatic core, plugin, theme or translation updates. That includes security releases, which WordPress applies on its own by default.

What changes in .git detection

WordPress has always skipped automatic updates when it finds a .git, .svn, .hg or .bzr directory in the install or in any folder above it. The reasoning is that if the code is versioned, the repository is what gets updated, and the server should not write files on its own.

Up to 7.1, WP_Automatic_Updater::is_vcs_checkout() only recognized those names when they were directories. In a Git worktree or submodule, .git is a plain file pointing to the main repository, so those sites were treated as not under version control and kept updating themselves. In 7.2, the function and the matching Site Health test switch to file_exists(): the entry only has to exist, as a file or a directory. The contents of the .git file are not read.

The practical effect shows up with the first security release after a site moves to 7.2. On November 18, WordPress 7.1.5 shipped with 20 items in its security section, and the announcement notes that sites with automatic background updates get the release without intervention. A 7.2 site running from a worktree will stay on the previous version until someone updates it.

Who needs to check

The change hits teams that ship WordPress to the server through Git and keep .git as a file in the site folder or above it. The note names two cases: the site folder is a Git worktree, or the install is a submodule inside a larger repository.

Sites that already had a .git directory in the install are unaffected, because they were already excluded from automatic updates. Nothing changes either for teams that push files to the server without Git metadata, through rsync, a package or a container image, or for managed hosting that does not use Git in the site folder.

In my assessment, the biggest risk sits with agencies and small teams that set up Git deploys years ago and, without noticing, rely on WordPress automatic updates to cover security fixes between deploys.

What to decide before December 8

The first step is to find out whether any site is in this situation. On the server, look for a .git file (not a directory) in the install folder and the folders above it. After moving to 7.2, Site Health and the updates screen show the reason when automatic updates are skipped.

For each site you find, there are two ways out:

  1. Own updates through the repository. Someone has to track WordPress and plugin security releases and deploy them within a few days. This is the behavior core now expects from a versioned site.
  2. Keep automatic updates with the automatic_updates_is_vcs_checkout filter returning false (for example, add_filter( 'automatic_updates_is_vcs_checkout', '__return_false' ); in a mu-plugin). The cost is that the server starts changing files the repository does not know about, and the next deploy can undo a security fix if the repository was not updated first.

The second option keeps today's behavior. The first fits a Git deploy better, but it only works if a person or routine has a set deadline to apply fixes.

What is still open

7.2 is at release candidate stage. The December 8 date comes from the RC1 announcement, and changes like this can be revisited before the final release, although the note already treats the behavior as part of 7.2.

The note covers only core's automatic updater. It says nothing about updates triggered by WP-CLI or hosting dashboards, and there are no figures on how many sites run from a worktree or submodule. If you depend on one of those tools, confirm with the vendor how it behaves on 7.2.

If your company is weighing something similar, reach me on LinkedIn or WhatsApp.

References

Aerial view of a snow-covered pine forest crossed by a straight road that runs over a frozen stream

Photo by Jane Palash on Unsplash

#Operations, #Radar