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.

Johan van der Wijk

This plugin disables all WordPress updates (core, plugins and themes). This can be useful if you have multiple environments such as a live and staging server and you don’t want your users to use the update functionality.
This plugin not only disables the update mechanism for the core, plugins and themes, but it also removes the update menu item from the left navigation menu in the admin dashboard.

Disable Updates for WordPress Core, Plugins and Themes

Disables the WordPress update checking and notification system for all core, plugin and theme updates.

Forced Auto Updates vs Disable Updates for WordPress Core, Plugins and Themes