lelandf

By default, WordPress will not apply <a href="https://codex.wordpress.org/Configuring_Automatic_Background_Updates" rel="nofollow ugc">automatic background updates</a> if it detects a version control system (like Git or Subversion) in the WordPress directory or any of its parent directories.
WordPress does this because it assumes that if version control systems are present, the site owners have their own system in place for managing updates, and WordPress doesn’t want to mess with that.
However, minor updates can contain critical security vulnerability fixes, and those aforementioned site owners may consider the benefit of having minor releases automatically updated by WordPress greater than the risks of waiting too long to apply those updates themselves.
If that sounds like you, then you may wish to consider installing this option-free plugin.
Just activate when you need it.
Perhaps before a “disconnected” vacation when you don’t want to run the risk of a security update being released during it, and having no way of applying said update until your return.
Deactivate it when you don’t.

Forced Auto Updates

Apply automatic background updates for minor releases of WordPress core, even with version control systems present.

simshaun

There’s not much to this plugin. It’s a couple barebones filters that turn off the plugin and theme autoupdate emails.
On WordPress 5.5.0, plugin/theme autoupdate emails are turned off regardless of whether or not they failed.
Since WordPress 5.5.1, emails indicating update failures are allowed through.

Disable Plugin Autoupdate Emails

Getting too many "plugin updated" or "theme updated" emails since WordPress 5.5? This turns them off.

Forced Auto Updates vs Disable Plugin Autoupdate Emails