Issue #3262359 by phenaproxima: Don't catalog event subscribers as a way of determining the validity of stored results

Issue #3262303 by phenaproxima: Always run readiness checks when modules are installed or uninstalled

Issue #3261847 by phenaproxima, tedbow: Add helpful methods to compute the difference between two ComposerUtility objects

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

Issue #3254207 by kunal.sachdev, phenaproxima, tedbow: Only allow 1 patch release update increment in Cron

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

Issue #3259822 by phenaproxima: ComposerUtility should use the installed/local repository to get package info

Issue #3259228 by phenaproxima, tedbow: Add functional test coverage of Stage::require() to ensure only the correct dependencies are updated

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

Issue #3258045 by phenaproxima: Ensure update command in Stage::require() only updates specified packages

This reverts commit a941773c.

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

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

Issue #3250386 by tedbow, phenaproxima: Ensure that the stage is uniquely idenitfiable across multiple sessions

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

Issue #3250136 by phenaproxima, tedbow: Allow package_manager_bypass to record method invocations for functional tests

Issue #3247478 by tedbow, phenaproxima: Only pre-operation events should be able to flag errors that stop an update