Issue #3293381 by phenaproxima, tedbow: If cweagans/composer-patches is installed, require composer-exit-on-patch-failure

Issue #3291147 by phenaproxima, tedbow, effulgentsia, heddn: Successfully applying an update puts the remainder of the request into an unreliable state

Issue #3277035 by phenaproxima, tedbow, chrisfromredfin: Create a validator to check for  symlinks anywhere in the project

Issue #3274892 by phenaproxima, tedbow: Before applying the update, check that any needed changes to the site directory are possible

Issue #3280180 by phenaproxima, tedbow: Consolidate all version validation logic into a single class

Issue #3275317 by phenaproxima: If you change the path to the Composer executable, you may still see out-of-date validation errors

Adam G-H authored 2 years ago and Ted Bowman committed 2 years ago

Issue #3272060 by phenaproxima: Use route option to determine if readiness checks should be shown on a route

Issue #3254755 by tedbow, kunal.sachdev, phenaproxima: Add a seperate Update recommender and update version validator for cron updates

Kunal Sachdev authored 3 years ago and Adam G-H committed 3 years ago

Issue #3266092 by kunal.sachdev, tedbow, phenaproxima: Make sure staging root is unique for each Drupal site

Issue #3257845 by phenaproxima: Clear readiness stored readiness check results after an update is applied

Ted Bowman authored 3 years ago and Adam G-H committed 3 years ago

Issue #3255320 by tedbow, phenaproxima: ReadinessCheckEvent should have CronUpdater instance when cron will run

Ted Bowman authored 3 years ago and Adam G-H committed 3 years ago

Issue #3258661 by tedbow, phenaproxima: use \Drupal\package_manager\Stage::getActiveComposer() instead of path locator service to get active composer where possible

Ted Bowman authored 3 years ago and Adam G-H committed 3 years ago

Issue #3252126 by tedbow, phenaproxima: Do not apply updates during cron if there are DB updates in the staging area

Issue #3250696 by tedbow, phenaproxima: Each stage should have its own staging directory, to avoid filesystem and locking conflicts

Issue #3249517 by phenaproxima: Ensure that all Automatic Updates event subscribers only apply to Automatic Updates uses

Issue #3227122 by tedbow, phenaproxima: Create a lock system to ensure only 1 update can be attempted at a time

Kunal Sachdev authored 3 years ago and Adam G-H committed 3 years ago

Issue #3242724 by kunal.sachdev, phenaproxima, tedbow: Ensure cron runs frequently enough to run updates