Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-64409

Update composer.json with the new moodlehq/behat-extension tag for 3.7dev

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide

      In the master branch only:

      Test 0

      1. Skip this step, nothing to do, dear tester, integrators will deal with this. Verify that both phpunit and behat runs are installing and passing ok for master.

      Test 1
      (better use composer >= 1.3, to avoid some time format differences)

      1. Open a terminal and navigate to your moodle root directory.
      2. Run php composer.phar update
      3. Open composer.lock on a text editor.
      4. You SHOULD find
        "name": "moodlehq/behat-extension",
        "version": "v3.37.0",
        with "url": "https://github.com/moodlehq/moodle-behat-extension.git",
      5. Back on your terminal, delete the "vendor" folder and "composer.lock". Also remove composer caches.

        rm -rf vendor
        rm composer.lock
        php composer.phar clearcache
        

      6. Run again php composer.phar update
      7. Open composer.lock on a text editor
      8. You SHOULD find
        "name": "moodlehq/behat-extension",
        "version": "v3.37.0",
        with "url": "https://github.com/moodlehq/moodle-behat-extension.git",

      Note: the local run of composer update may lead to some other small differences (git diff composer.lock) if some dependency packages were updated the last hours @ packagist. They can be ignored, unless there is something really big detected.

      Show
      In the master branch only: Test 0 Skip this step, nothing to do, dear tester , integrators will deal with this. Verify that both phpunit and behat runs are installing and passing ok for master. Test 1 (better use composer >= 1.3, to avoid some time format differences) Open a terminal and navigate to your moodle root directory. Run php composer.phar update Open composer.lock on a text editor. You SHOULD find "name": "moodlehq/behat-extension", "version": "v3.37.0", with "url": "https://github.com/moodlehq/moodle-behat-extension.git", Back on your terminal, delete the " vendor " folder and " composer.lock ". Also remove composer caches. rm -rf vendor rm composer.lock php composer.phar clearcache Run again php composer.phar update Open composer.lock on a text editor You SHOULD find "name": "moodlehq/behat-extension", "version": "v3.37.0", with "url": "https://github.com/moodlehq/moodle-behat-extension.git", Note: the local run of composer update may lead to some other small differences ( git diff composer.lock ) if some dependency packages were updated the last hours @ packagist. They can be ignored, unless there is something really big detected.
    • Affected Branches:
      MOODLE_37_STABLE
    • Fixed Branches:
      MOODLE_37_STABLE
    • Pull from Repository:
    • Pull Master Branch:

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  13/May/19