-
Task
-
Resolution: Fixed
-
Minor
-
3.7
-
MOODLE_37_STABLE
-
MOODLE_37_STABLE
-
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.37.0 for Behat 3 and Moodle 3.7dev for example - 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, delete it, delete the vendor dir, run composer clearcache and, using the lower php version supported* by the .dev Moodle, run composer update (will take a while without caches).
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.
* Note that, for Moodle 3.7 will be moving to PHP 7.1 as minimum supported version (see MDL-63276)... so we'll be generating the composer.lock file with that php version.
- blocks
-
MDL-64530 Bump Travis max version to 7.3
- Closed
- has a clone
-
MDL-65810 Update composer.json with the new moodlehq/behat-extension tag for 3.8dev
- Closed
- has been marked as being related by
-
MDL-63276 Decide Moodle 3.7 requirements and push them to environment.xml (due date: 2018-12-17)
- Closed
- is a clone of
-
MDL-62620 Update composer.json with the new moodlehq/behat-extension tag for 3.6dev
- Closed
- is blocked by
-
MDL-63276 Decide Moodle 3.7 requirements and push them to environment.xml (due date: 2018-12-17)
- Closed