Requirements Ability to edit the source code during upgrades. Ability to execute both web and CLI upgrades. Scenario 1: Web upgrade triggered by the plugin version bump Ensure that your test Moodle install is fully up to date by going to Admin / Notifications. Save the attached environment.xml file into the blocks/html folder. Edit blocks/html/version.php and increment $plugin->version by 1. Go to Admin / Notifications. Verify that you see the environment check page, with title 'Current release information' and that it complains that you do not have PHP 9 installed! Edit the blocks/html/environment.xml file, to change 9.0.0 to 7.0.0 and click reload. Verify you see an all-green environment check page. Click continue. Verify that you see the plugin check page. No need to complete the upgrade. Scenario 2: CLI upgrade triggered by the plugin version bump Ensure that your test Moodle install is fully up to date by going to Admin / Notifications. Save the attached environment.xml file into the blocks/html folder. Edit blocks/html/version.php and increment $plugin->version by 1. Execute the CLI upgrade. This will depend on your environment, but generally it is something like $ sudo -u www-data php admin/cli/upgrade.php Verify that you see the "== Environment ==" section with the "!! php !!" check failed because the "Block / HTML" plugin required you to have PHP 9 installed and the upgrade does not happen. Edit the blocks/html/environment.xml file, to change 9.0.0 to 7.0.0 and run the upgrade again. Verify the upgrade can continue normally without any environment errors reported (note that CLI does not show the "ok" checks) Remember to delete blocks/html/environment.xml and reset the version number in blocks/html/version.php.