-
Task
-
Resolution: Fixed
-
Minor
-
3.10
-
MOODLE_310_STABLE
-
MOODLE_310_STABLE
-
Special notes (for this issue only):
Note: This must be done for as many dev branches still not having their corresponding tags. Normally it's only master, but under parallel development periods, when it could be (together with or alternatively) an XXX_STABLE dev branch. Of course it requires the dev branches to exist, cannot be done before that.
^^^ In this case, it's together with the 311_STABLE branch, master too.
After releasing XY we should update composer.json in master to point to a new tag (from https://github.com/moodlehq/moodle-behat-extension.git master branch) according to the moodle development version (3.310.0 for Behat 3 and Moodle 3.10dev for example - and 3.400.0 for Behat 3 and Moodle 4.0dev - this issue).
Detailed process:
https://docs.moodle.org/dev/Release_process#2_weeks_after
After creating the branch & tag and pushing it upstream... verify the new version has been released in packagist (it happens automatically - hooks are enabled since v3.36.x - or under demand if a package maintainer is asked). Link:
https://packagist.org/packages/moodlehq/behat-extension
Then, in the master branch, edit composer.json and bump the "moodlehq/behat-extension" to the newly created tag.
To regenerate the composer.lock file, follow the instructions available @ Moodle Docs.
Ensure changes related to the extension are ok in the .lock file (version, pointing to moodlehq repo...). It will come also with updates to many of the dependencies. Run behat tests and phpunit tests to confirm they work ok.