Problem/Motivation
In #3254207: Only allow 1 patch release update increment in Cron we found out that we need a method in UpdateRecommender to recommend release during cron because in the form it’s better to recommend the most recent patch to the installed minor.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork automatic_updates-3254755
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 #2
tedbow#3252190: Store all installable releases in update_calculate_project_update_status() would make it possible for use to always recommend the latest in the current minor.
but even before then if the update recommends a version in the next minor we can check if there is security release in the current minor.
This would mean that before we have 3252190 then a site could update via composer to keep there site on the latest patch releases but if I security release happen cron would update to it.
Comment #5
tedbowI am in middle of work on this
Comment #6
tedbowComment #7
tedbowComment #10
tedbowComment #11
phenaproximaComment #12
phenaproximaComment #13
phenaproximaWhew. There are some small things I'd like to clean up, but this is already a major refactoring of some important parts of the system, and I think it's gone on long enough. I'm happy overall with what @tedbow and I cooked up here. RTBC!
Comment #14
tedbowComment #16
tedbow🥳
@phenaproxima thanks for sticking with this one!