You run many Drupal test instances on your server, on which you run frequent cron executions? You can relieve it, as we did thanks to the Sleepy Cron module: https://www.drupal.org/project/sleepy_cron
Sleepy Cron
This module aims to preserve server resources (processors, memory, thus electricity) by not running the cron on websites that are not used.
@wimleers@tedbow@phenaproxima As a mitigation, we can expect test instances to not be publicly available, and as soon as the test instance is used again, cron runs and updates are found.
@gaelg@wimleers @[email protected] yeah Automatic Updates don't seem critical for the use cases described but you could also setup a separate server cron job that runs our update terminal command that finds and runs updates