
Problem/Motivation
For Core MVP we had initially planned to only support patch level updates.
I chatted with @xjm recently who suggested we could have a non-UI config setting to allow minor updates.
I think this sounds great.
Currently we disallow updates that have database updates required during cron. We should not allow minor updates via cron. They will likely need database update anyways.
Proposed resolution
- add
allow_core_minor_updates
config switch. This switch is core specific to allow core have a different switch once we support config updates in core - Add warning at the start of minor update with reasons why the user should be more careful. Is there an existing documentation page for this?
- Change
\Drupal\automatic_updates\Validator\UpdateVersionValidator
to allow minor updates if config is set and not in cron - Add warning in update apply form if an update DB update is detected.
- re-route the user to update.php after the update if there are DB updates.
4 and 5 are existing problems because only stop updates with DB updates in cron so we should solve those first.
Issue fork automatic_updates-3259664
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
tedbowComment #4
tedbowComment #6
phenaproximaComment #7
phenaproximaAfter discussion with @tedbow, we agreed to postpone this on #3260368: Improve the UX for updates that require database changes.
Comment #8
phenaproximaBlocker is in.
Comment #9
tedbowIs there a documentation page we link to if I minor update is recommended? Something to explain the differences between patch and minor updates and why a minor update could be more disruptive?
Maybe since this is hidden feature this could be a follow up
Comment #10
tedbowComment #12
phenaproximaForgot to credit myself; whoops!