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

Issue #3245846 by phenaproxima, tedbow: Move ExcludedPathsTrait to pre-create and pre-apply events in Package Manager

Issue #3244976 by phenaproxima, tedbow: Add a Stage service to Package Manager, which defines the life cycle of a staging area for updates and installs

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

Issue #3241105 by phenaproxima, tedbow: Ensure core package is validated in readiness check and pre-start

Issue #3238647 by phenaproxima, tedbow: Create an API for easily accessing relevant Composer information

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

Issue #3236299 by kunal.sachdev, phenaproxima, Suresh Prabhu Parkala, tedbow: User should not be allowed to do update if it is from minor version to another minor version

Kunal Sachdev authored 3 years ago and Ted Bowman committed 3 years ago

Issue #3238717 by kunal.sachdev, phenaproxima: Replace the uses of \Drupal::service with dependency injection in ReadinessValidationManager wherever possible 

Issue #3233587 by phenaproxima, tedbow: Create a build test that tests calling API as cleanly as possible

Issue #3230668 by phenaproxima, tedbow: Split out Composer Stager wiring into Package Manager submodule

Issue #3230049 by phenaproxima, tedbow: Add validation subscriber to check that Composer can be found