A major WordPress release is the moment every plugin and theme on your site meets code they have never run against. Most of them are fine. The ones that are not get fixed within days – and a site that installed the release on day one is the one that found out the hard way.

Digitizer Update Hold gives your site a simple rule: a major release waits, a security release does not.

What it does

Holds a major release – 7.0 to 7.1, say – for a set number of days after your site is first offered it. 30 by default; you choose.
Never holds security or maintenance releases – 7.1 to 7.1.1. Those are what keeps a site safe, WordPress installs them on its own, and this plugin does not look at them.
Removes the held release from the update offer rather than merely warning about it. A warning does not stop someone pressing the button; a button that is not there does.
Shows you the hold. The Updates screen and the dashboard say which release is held, when your site first saw it, and when the hold ends – so a held update is never mistaken for a broken one.
Lets you lift it. One click offers the release immediately, permanently for that release line. 7.1.1 arriving a week later will not ask you again.
Installs nothing on its own. When the window passes, the release is simply offered again. Updating stays your decision.

What it does not do

It makes no network requests. Not to WordPress.org, not to anyone. The window is counted from the day your site first saw the release, which your site already knows.
It does not install, download, or modify any code.
It sends no data anywhere. There is nothing to send.
It does not touch plugin or theme updates. Only WordPress core, and only major releases.

Multisite

A core update is network-wide, so the hold is too. The plugin is network-activated, its settings live under Network Admin > Settings, and only a network administrator can change the hold or lift one.